Hi Tiemo, It unlocks at the end of a handler. This can be a problem when calling another handler.
I handle it by turning a called handler into a function. However, I don't think you can do it with a "send in time" handler. Sent from my iPhone > On Jul 5, 2017, at 7:45 AM, Tiemo Hollmann TB via use-livecode > <use-livecode@lists.runrev.com> wrote: > > Hello, > > Is this possible? > > > > on handler1 > > lock screen > > -- do some stuff here > > send "handler2" in 0 milliseconds > > end handler1 > > > > on handler2 > > -- do some other stuff here > > unlock screen > > end handler2 > > > > in my real case the screen seems to be unlocked before handler2 has finished > and I can see some updates on the screen, while the two handlers are > running. The docs don't say, that there is an automatic unlock screen at the > end of each handler and I checked my code that each lock has one unlock. > > Should this be possible, or are there other statements/functions, which > unlock the screen by default beside of modal a stack? > > Thanks > > Tiemo > > > > > > > > _______________________________________________ > 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
