Android: List Field and Native Scroller

[Ken Corey]

That delay seems to be the best choice...how else can you tell if the 
user (moving in human-time) is going to drag a finger?  You don't unless 
you wait a little while.

In a web browser, sometimes you don't care about scrolling, you can try 
to remove the wait this way:

http://cubiq.org/remove-onclick-delay-on-webkit-for-iphone

Or you can respond to the touchstart events, rather than the click events.

I don't know how often this translates to Livecode though.

-Ken

On 03/07/2012 02:18, Ralph DiMola wrote:
>           Is there a way around this?  I know there must be...  How do you
> get it to scroll when it should scroll, and "tap" when it should tap?
>
> I found that if I stored the current milliseconds while scrolling is
> occurring and made sure that 250 milliseconds have passed since the last
> movement it worked. And I mean perfectly. I have had no false taps or missed
> taps since. In fact it is as good as it gets from the user experience.
> (Thanks RR!!!!)
>
> If anyone else has made it work without the .25 second test, please chime
> in.