One situation in particular is when you make changes to numerous objects via a single script, such as grouping, changing location, scaling, etc. These cases will almost always execute faster when lock messages is true because the IDE (and/or scripts that track objects and their properties) won't update until messages are unlocked. Locking the screen helps, but locking messages helps more.
Regards, Scott Rossi Creative Director Tactile Media, UX Design On 10/15/12 3:38 PM, "Bob Sneidar" <b...@twft.com> wrote: >I'd be curious if people can summarize all the times that locking >messages became a necessity, and then see if some of us can figure out >"another way of going about it". _______________________________________________ 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
