That doesn't sound right, though I've seen issues with nested locks too.
What happens if you call this handler:
on unlockReally
repeat until the lockscreen is false
unlock screen
end repeat
end unlockReally
On 8/18/17 3:54 PM, Bob Sneidar via use-livecode wrote:
okay after some testing it seems only the script that locked the screen, maybe
only the actual handler can clear it's own lock. If this is not right I'd like
to know it. Seems there ought to be an unlock all command or some such thing.
Bob S
On Aug 18, 2017, at 13:37 , Bob Sneidar via use-livecode
<[email protected]> wrote:
Hi all.
I have some screen updates I do that take time because I query a database
first, and it may not be local. To keep the screen from progressively updating,
I lock the screen.
<snip>
_______________________________________________
use-livecode mailing list
[email protected]
Please visit this url to subscribe, unsubscribe and manage your subscription
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode
--
Jacqueline Landman Gay | [email protected]
HyperActive Software | http://www.hyperactivesw.com
_______________________________________________
use-livecode mailing list
[email protected]
Please visit this url to subscribe, unsubscribe and manage your subscription
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode
