use-livecode Digest, Vol 230, Issue 17

Bob Sneidar bobsneidar at
Mon Nov 28 11:24:49 EST 2022

I can imagine a lock/unlock wrapper that registers every lock screen request and will only unlock the screen if called from the same handler or uses the same passed ID as the lock handler. You could have a property for each registered lock to allow or disallow override from another unlock. 

That may be too comlicated though. Is it possible to check if the screen is locked first? 

Bob S

> On Nov 23, 2022, at 09:42 , J. Landman Gay via use-livecode <use-livecode at> wrote:
> I like to surprise people. :) Basically I was hoping to avoid brute force, but it looks like import/export may be the best way. If I do the stacks only a few at a time I'll only need a dozen passes or so.
> Part of the problem was determining which locks need changing and which were not visual effects, or which were locked in one handler and unlocked in a handler that might be elsewhere, sometimes even in a different stack. Some manual examination seems required. Fortunately the latter is rare.
> --
> Jacqueline Landman Gay | jacque at
> HyperActive Software |
> On November 23, 2022 5:58:41 AM info--- via use-livecode <use-livecode at> wrote:
>> Hallo Jacqueline,
>> Well I wouldn’t expect you asking such a question..!
> _______________________________________________
> use-livecode mailing list
> use-livecode at
> Please visit this url to subscribe, unsubscribe and manage your subscription preferences:

More information about the use-livecode mailing list