To ensure that our screen doesn’t accidentally get overlocked, even though the system may unlock it at idle time, the best practice is to always unlock it at the proper time within you code. That way you can’t confuse things and find yourself scratching your head as to why it looks like your code isn’t working.
On a side note, just a point about proper computer grammar here: That should read: "Lock increments the counter, and unlock decrements the counter.” Excrement is a Doctor’s term. We don’t want our code to “excrement” anything! Yuk! LOL Thanks for the laugh! Rick > On Jan 22, 2021, at 10:59 AM, doc hawk via use-livecode > <firstname.lastname@example.org> wrote: > > Not so much either/or as it’s a counter, with 0 being unlocked. > > Lock increments the counter, and unlock excrements. > > The counter gets set to 0 when the engine idles, as well > > -- > Dr. Richard E. Hawkins, Esq. > (702) 508-8462 > _______________________________________________ > use-livecode mailing list > email@example.com > Please visit this url to subscribe, unsubscribe and manage your subscription > preferences: > http://lists.runrev.com/mailman/listinfo/use-livecode _______________________________________________ use-livecode mailing list firstname.lastname@example.org Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode