So I am gathering that used at the right times and in the right ways, globals and lockMessages both have their place. What we are lacking is a kind of global that is not IDE wide, and the ability to lock messages and still have our custom properties work. Seems like that is doable. If there is an enhancement request up I will vote for it.
Bob On Oct 15, 2012, at 4:41 PM, Peter Haworth wrote: > If you want to set the menuhistory of an option menu button without > triggering a menuPIck event, lock messages achieves that. > Pete > lcSQL Software <http://www.lcsql.com> > > > > On Mon, Oct 15, 2012 at 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 _______________________________________________ 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
