Bob.
Reread the thread on this. I posted at the getgo: repeat until the lockScreen is "false" unlock screen end repeat This has been echoed by others, correctly. You cannot guarantee that your screen will be unlocked with that one-liner. Unless you get back to idle, multiple locks are queued, and the screen will remain locked until they are all purged. The merits of this were discussed last week. Different users lock their screens for different reasons, and the "pending" locks are either a bonus or a chore. But you have to know they work this way. Craig -----Original Message----- From: Bob Sneidar <b...@twft.com> To: How to use LiveCode <use-livecode@lists.runrev.com> Sent: Mon, Sep 24, 2012 12:24 pm Subject: Re: lock/unlock screen Good idea. I myself have not encountered a situation where I need multiple handlers that lock the screen. Everything I do is database oriented anyway, so there is inevitably lots of idle times. If I ever do need this your idea seems the most reasonable way to go. Bob On Sep 21, 2012, at 8:42 PM, Kay C Lan wrote: > On Fri, Sep 21, 2012 at 5:47 AM, Bob Sneidar <b...@twft.com> wrote: > >> Face it Richmond. It's you and me against the world. ;-) > > > If you can't sleep at night because you're worried about multiple lock > screen, or keeping track of pairs, why not: > > if the lockScreen is false then lock screen _______________________________________________ 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
