2022 11:25 AM
To: How to use LiveCode
Cc: Bob Sneidar
Subject: Re: use-livecode Digest, Vol 230, Issue 17
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
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.
Tha
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 e
creen
>>>> -- do any number of things
>>>> unlock screen with
>>>>
>>>> These all need to be changed to:
>>>>
>>>> lock screen for visual effect
>>>> -- do any number of things
>>>> unlock screen with visual effe
