setProp and Lock messages
ambassador at fourthworld.com
Sun Dec 4 11:45:50 CST 2011
Todd Geist wrote:
> But I like all of these more than the alternative of using accessors on
> library stacks with name spaced accessors
> // or
> Although this is a lot less typing, I just don't care for it. Maybe I am
My apologies: I didn't mean to imply that using getProp/setProp was in
any way "stupid". On the contrary, for some problems they provide an
Those familiar with Cocoa's CoreData are no doubt impressed with the
power of name-value-pair (NVP) programming, some of which can be
simulated in LC with getProp/setProp. Nothing wrong with that at all.
That's one of the great things about LC: there are many ways to solve
problems, supporting a wide range of coding styles.
If you like NVP use it. The main point of my post was just the caveat
about how lockMessages can affect NVP-based systems. If your systems
can account for that there's certainly no harm in using getProp/setProp.
LiveCode training and consulting: http://www.fourthworld.com
Webzine for LiveCode developers: http://www.LiveCodeJournal.com
LiveCode Journal blog: http://LiveCodejournal.com/blog.irv
More information about the use-livecode