Feedback request: getProp/setProp and lockMessages
monte at sweattechnologies.com
Thu Nov 28 14:29:50 EST 2013
On 29/11/2013, at 6:24 AM, Robert Brenstein <rjb at robelko.com> wrote:
> I imagine that lockPropMessages would apply to all cases discussed earlier, so behavior would be consistent, and since locking will be done by the developer, said developer should know the consequences and use this only when required. Without the lock option, the problem situations, as discussed, would have no escape valve.
Are you talking about the recursion? If it were fixed in the engine to ensure setting the property from within a setProp hander anywhere in the path (not just in the object itself as is currently) did not trigger the handler again wouldn't that resolve the problem. There's also pass and setting the whole property set as options.
M E R Goulding - software development services
mergExt - There's an external for that!
More information about the Use-livecode