If you assign a name to the native control, mobileControlTarget() returns
it instead of the number. It's a handy way to match up native controls to
their LC counterparts without keeping a reference list.
Jacqueline Landman Gay | jac...@hyperactivesw.com
HyperActive Software | http://www.hyperactivesw.com
On July 5, 2016 6:03:49 PM Richard Gaskin <ambassa...@fourthworld.com> wrote:
Ralph DiMola wrote:
> This is what works for me....
...
> on scrollerDidScroll hScrolled, vScrolled
> local ControlID
> --answer "Here!"
> try
> put mobileControlTarget() into ControlID
> set the vscroll of control ControlID of stack "xxx" to vscrolled
> set the hscroll of control ControlID of stack "xxx" to hscrolled
> end try
> pass scrollerDidScroll
> end scrollerDidScroll
Now I'm confused. If mobileControlTarget() returns the ID of the native
scroller, how does that affect the scroll of a LiveCode object in the
subsequent lines?
Do we have control over mobile control IDs in a way that would allow
them to match LC object names or IDs?
--
Richard Gaskin
Fourth World Systems
Software Design and Development for the Desktop, Mobile, and the Web
____________________________________________________________________
ambassa...@fourthworld.com http://www.FourthWorld.com
_______________________________________________
use-livecode mailing list
use-livecode@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@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode
