Richard: I understand the intention of your suggestion, but aside from using setProp/getProp, what object properties *cannot* be set during locked messages? Has a reason ever been put forward from RunRev for why custom props cannot be set/read while messages are locked?
It seems to me that the current behavior has only been a behavior for some technical limitation in the engine, not because of a scripting need. But this is totally a perception on my part. Otherwise, I'm all for *some* (ANY) method for enabling custom prop setting/reading during locked messages. Best Regards, Scott Rossi Creative Director Tactile Media, UX Design On 10/15/12 12:40 PM, "Richard Gaskin" <ambassa...@fourthworld.com> wrote: >Monte Goulding wrote: > > > On 16/10/2012, at 6:21 AM, Richard Gaskin wrote: > > > >> If any script attempts to get or set a custom property while > >> the lockMessages is true, any getProp or setProp messages won't > >> be triggered. > >> > >> If such handlers are necessary for execution unexpected behaviors > >> will occur, and given the nature of such scripts tracking down > >> the cause of the errant behavior can be tricky and time-consuming. > > > > > > Do you consider this a bug in lockMessages? Perhaps set and getProps > > should be able to be marked in some way that they are required. I > > guess changing the behavior of lockMessages could cause issues. > >Agreed. But I like the idea of having a way to change that. > >Since the issue is specific to getProp and setProp, maybe there might be >a way to declare those as "required", e.g.: > >required getProp MyProp > >This would keep such a change optional, and limit its scope to only >those getProp and setProp handlers that are essential, since sometimes >it may be useful to have them suppressed by lockMessages. > >-- > Richard Gaskin > Fourth World > LiveCode training and consulting: http://www.fourthworld.com > Webzine for LiveCode developers: http://www.LiveCodeJournal.com > Follow me on Twitter: http://twitter.com/FourthWorldSys > >_______________________________________________ >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
