I’m sure someone else can be more clear, but when the engine gets to an idle state then locks should be cleared. In your example, it would probably clear at the end of that mouseUp handler, but aTest would completely run with the screen locked.
Sent from my iPhone > On Jan 22, 2021, at 3:57 AM, Terence Heaford via use-livecode > <use-livecode@lists.runrev.com> wrote: > > Just looking for clarity with regard to lock screen. > > Is there only one state for the screen, either locked or not locked and when > is that state changed. > > --------------- > on mouseUp > > lock screen > > aTest > > end mouseUp > > ---------------- > on aTest > > — is the screen still locked here > > end aTest > > ———————— > > At what point is unlock screen called by livecode without me calling it > directly. > > The docs say when all pending handlers have completed but what exactly is a > pending handler. > > > > Thanks > > Terry > _______________________________________________ > 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
