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.
-- M E R Goulding Software development services mergExt - There's an external for that! On 16/10/2012, at 6:21 AM, Richard Gaskin <ambassa...@fourthworld.com> 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. _______________________________________________ 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
