On Sunday, July 15, 2012, J. Landman Gay wrote: > > I got lost in your description, but I don't think the above will be a > problem. Locks are nested and the screen won't unlock until the last paired > "unlock" executes, provided no idle events occur (all locks are cancelled > on idle.) That means you won't see cards popping around as long as the > engine doesn't get a chance to do any messaging. > > > Oh, in that case . . "Oh, neve mind."
:) Thank yo. That raises the question, though--do I need to worry about ever "leaving" an extra lock lying around? It sounds like reaching an idle state will take care of that for me. Thanks greatly -- The Hawkins Law Firm Richard E. Hawkins, Esq. (702) 508-8462 hawkinslawf...@gmail.com 3025 S. Maryland Parkway Suite A Las Vegas, NV 89109 _______________________________________________ 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
