scrolling to a line
charles.hartman at conncoll.edu
Sun Nov 13 14:21:50 CST 2005
On Nov 13, 2005, at 3:04 PM, Dan Shafer wrote:
> FWIW, I don't think that's expected behavior or necessarily good
> user experience design. If there's no "find" then things should
> stay the same. Maybe a beep but a scroll to a phantom location
> doesn't really help me much, doesn't give me any new information.
Well, it tells you one thing: there's no entry like what you just
typed. In my case, the user may be double-clicking a line to choose
it, or pressing an "Add New" button if the thing isn't found.
>> But it doesn't solve one problem: suppose the user starts typing a
>> string that doesn't appear in the list? If the first few letters
>> match something, this scrolls to pretty close. But suppose nothing
>> starts with 'Q' and the user starts by typing a 'q'? The list
>> won't scroll at all. What would be nicer would be to scroll to the
>> place where an item beginning with 'q' *would* be if there were one.
More information about the use-livecode