Hi All

I haven't seen anyone else mention this problem or even get involved in a
discussion here except for Bob to confirm it.
It is a FUNDAMENTAL problem.

@Jacque since you deploy (if memory serves) large android apps  , can you
confirm the error and @Panos is there a
workaround or a fix coming anytime soon?

For IOS 13 we have to use the latest and it is a real pain to work out when
the  Android scroller went wrong within the
V 9 series. - never mind having to have multiple environments to compile
with.

This is a SHOWSTOPPER we have been mostly testing the IOS apps that work
and all of the Android stuff worked
if we didn't have a "long" list that needed to scroll and select. Only
noticed with "Real" data with a long list.

Gone back to 9.5 and the problem is still there.

will try 9.05 and see what happens.

Looks from our testing  that the  ScrollerBeginDrag and ScrollerEndDrag are
not being fired.
Regards Lagi



On Fri, 6 Dec 2019 at 14:51, Sannyasin Brahmanathaswami via use-livecode <
[email protected]> wrote:

> On 9.6 dp 1  I was testing on iOS for a week.
>
> Then I tested on Android. Surprising new behavior in the mobileScroller:
>
> It receives the mouseDown as soon as you scroll, or mouseUp after you
> scroll. This does not happen on iOS, not did in happen in 9.5 on Android.
>
> How can I prevent this and only trigger a "touch" when the user is not
> scrolling?
>
> BR
>
>
> _______________________________________________
> use-livecode mailing list
> [email protected]
> Please visit this url to subscribe, unsubscribe and manage your
> subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode
>
_______________________________________________
use-livecode mailing list
[email protected]
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Reply via email to