Re: Android Touchscreen Malfunction

2017-05-16 Thread Phil Davis via use-livecode
I assume flushEvents() isn't available for mobile? At least the 8.1.3 dictionary shows it is for desktop only. So would something like this work? local sTaskStatus, sTaskRequests on mouseUp send "doTask" to me in 0 seconds put the result & CR after sTaskRequests end mouseUp

Re: Android Touchscreen Malfunction

2017-05-16 Thread Paul Dupuis via use-livecode
On 5/16/2017 4:32 PM, Richard Gaskin via use-livecode wrote: > Paul Dupuis wrote: > > > in your handler for mouseDown (or mouseUp) check the pendingMessages > > (see Dictionary if unfamiliar with pendingMessages) for any other > > mouseDown (or mosueUp) messages pending for the same object and the

Re: Android Touchscreen Malfunction

2017-05-16 Thread Richard Gaskin via use-livecode
Paul Dupuis wrote: > in your handler for mouseDown (or mouseUp) check the pendingMessages > (see Dictionary if unfamiliar with pendingMessages) for any other > mouseDown (or mosueUp) messages pending for the same object and the > one executing. Wouldn't the pendingMessages be limited to timers?

Re: Android Touchscreen Malfunction

2017-05-16 Thread Paul Dupuis via use-livecode
On 5/16/2017 2:55 PM, Alejandro Tejada via use-livecode wrote: > Hi All, > > Recently, while testing a stack in an Android Phone, > I found with surprise that mouseup and mousedown > messages were triggered very fast (2 or 3 times in > succession). > > After checking the phone screen, I noticed a

Android Touchscreen Malfunction

2017-05-16 Thread Alejandro Tejada via use-livecode
Hi All, Recently, while testing a stack in an Android Phone, I found with surprise that mouseup and mousedown messages were triggered very fast (2 or 3 times in succession). After checking the phone screen, I noticed a small (almost unnoticeable) crack in the corner. How could we change our