On Thu, Sep 20, 2012 at 8:30 AM, Bob Sneidar <b...@twft.com> wrote: > I agree with Richmond. I cannot think of a case where I would want to lock a > screen multiple >times and then incrementally unlock the screen, knowing that the screen is >still locked!
I have several; it's quite common in what I'm writing. I have routines that want the screen locked that have other routines that want the screen locked. Those secondary routines, though, sometimes are called from different places from which the screen is not already locked--these can safely do an unlock, without worrying about whether or not they're nested, or by how many levels. -- 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
