Yup. My troubles came when I had a handler unlock the screen 5 times straight and I do not lock the screen to that many levels. It still did no unlock the screen, so now it may be that one handler cannot unlock another handler's lock screen, which I was unaware of.
Bob S > On Aug 18, 2017, at 18:37 , Mark Wieder via use-livecode > <use-livecode@lists.runrev.com> wrote: > > On 08/18/2017 03:50 PM, Bob Sneidar via use-livecode wrote: >> Hard to say. I'm almost done finding every place I lock the screen and >> adding an unlock screen in the same handler. > > And that, of course, is the best procedure. Locking/unlocking the screen > works on sort of a reference-counting approach. In general, locking the > screen increments a counter, unlocking the screen decrements it. When the > counter reaches zero, the screen is unlocked and all the pending updates take > place. > > -- > Mark Wieder > ahsoftw...@gmail.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
