View Single Post
epage's Avatar
Posts: 1,684 | Thanked: 1,562 times | Joined on Jun 2008 @ Austin, TX
#20
Originally Posted by mcdull View Post
Click is registered only when the finger/stylus leaves the screen, tha'ts how it has been doing in any system.

So, like in kinetic scrolling, if you have moved/dragged the finger before removing from the screen, it's registered as scroll. If you finger stays around the same area and released, it's registerd as click.

The scrolll bar works the same, you can't use it as regular scroll bar by clicking a point on the scroll bar to jump to that section, but you can still drag the scroll bar button to move up and down and from top to bottom really quick. If you release the finger wihout moving in the scroll bar's senitive area, it triggers a click on that location.
So let's see if I get this. What you are basically purposing is that there is a reserved area where the normal kinetic operations are turned into scroll operations? Kind of like how some trackpads on laptops have a special area for scrolling verse mouse movement?

So its not a full traditional scrollbar and does not cause application interference anymore than kinetic scrolling does.

I find it interesting. The main concern I would have is discoverability. Users might just perceive it as arbitrary/random behavior

I guess it would also cause issues with users having to care where they do their kinetic swipes.
__________________
770, n810, n900, Ideapad S10-3t
TheOneRing, DialCentral, Gonvert, Quicknote, Multilist, ejpi, nQa, Waters of Shiloah
Programming Blog

Last edited by epage; 2010-02-10 at 17:47. Reason: Typo