Odd native scroller issue on iOS

Terry Judd terry.judd at unimelb.edu.au
Thu May 19 01:33:20 EDT 2016


Scott, you are an absolute legend! Setting the vScroll of the scroller to
itself when the scroller is initialised didn't help (the routine to create
all native controls is called in  an openCard handler) but applying your
workaround each time one of the form elements is toggled (and the
contentRect is updated) seems to do the trick.

Grazie mille!

Terry…

Terry Judd  | Senior Lecturer in Medical Education
Department of Medical Education
<http://medicine.unimelb.edu.au/medical-education>
The University of Melbourne <http://www.unimelb.edu.au>
M: 0435 961 594  |  E: terry.judd at unimelb.edu.au
<mailto:tsj at unimelb.edu.au>
Publications 
<https://scholar.google.com.au/citations?user=XC5s6wwAAAAJ&hl=en>



On 19/05/2016 2:57 pm, "use-livecode on behalf of Scott Rossi"
<use-livecode-bounces at lists.runrev.com on behalf of
scott at tactilemedia.com> wrote:

>Try setting the vScroll of the scroller to itself (its current value) upon
>opening the card or after creating the scroller.  Goofy, yes, but doing so
>may solve the problem.
>
>Regards,
>
>Scott Rossi
>Creative Director
>Tactile Media, UX/UI Design
>
>
>
>
>On 5/18/16, 9:11 PM, "use-livecode on behalf of Terry Judd"
><use-livecode-bounces at lists.runrev.com on behalf of
>terry.judd at unimelb.edu.au> wrote:
>
>>I¹m having an issue with a native scroller on iOS. It¹s used to scroll a
>>group of expanding and contracting form elements that each contain a
>>number of Œon/off¹ buttons. It all works well enough (with the
>>contentRect of the scroller being adjusted each time an element is
>>expanded or contracted) except under certain circumstances, where some of
>>the elements (typically above a particular point in the form) become
>>unresponsive to mouse/touch events. The only way to get things happening
>>again is to Œjiggle¹ the scroller with your finger.
>>
>>The problem is definitely related to the native scroller because if I
>>turn it off and resort to a LC scroller it never happens. With the
>>scroller on, the contentRect always appears to report the correct
>>dimensions but even though it (contentRect) doesn¹t include a strip down
>>the side of the screen where the controls for toggling the elements are
>>located these are still affected when the problem occurs. Controls that
>>are above the contentRect area (i.e. nearer the top of the screen) are
>>never affected.
>>
>>Before I file a bug report, has anyone seen anything similar or have any
>>suggestions for working around the problem. I feel like I¹ve tried
>>everything up to this point but maybe not.
>>
>>Terry
>>
>>Terry Judd  | Senior Lecturer in Medical Education
>>Department of Medical
>>Education<http://medicine.unimelb.edu.au/medical-education>
>>The University of Melbourne<http://www.unimelb.edu.au>
>>M: 0435 961 594  |  E:
>>terry.judd at unimelb.edu.au<mailto:tsj at unimelb.edu.au>
>>Publications<https://scholar.google.com.au/citations?user=XC5s6wwAAAAJ&hl
>>=
>>en>
>>_______________________________________________
>>use-livecode mailing list
>>use-livecode at lists.runrev.com
>>Please visit this url to subscribe, unsubscribe and manage your
>>subscription preferences:
>>http://lists.runrev.com/mailman/listinfo/use-livecode
>
>
>
>_______________________________________________
>use-livecode mailing list
>use-livecode at lists.runrev.com
>Please visit this url to subscribe, unsubscribe and manage your
>subscription preferences:
>http://lists.runrev.com/mailman/listinfo/use-livecode



More information about the Use-livecode mailing list