Thanks to all who answered to my question.
I pretty quickly discovered by myself that setAprop was the solution.
To the question of Tom, whether I use it in a behaviour or a parent script:
Parent script is the answer. And to Irv's concern that my approach would
break encapsulation, I am not sure.
What I am doing is the following:
I have a handler in an parent script that gets a property list of possible
properties as a parameter, then steps through this list, checks, if the
script object has a property of the same name, if so, changes its value.
Like this:
on mChangeProp me, paramL
n = paramL.count
if n > 0 then
repeat with i = 1 to n
myProp = paramL.getPropAt(i)
myValue = paramL[i]
if me.getAProp(myProp) <> VOID then
setaProp(me, myProp, myValue)
end if
end repeat
end if
end
The handler is called from outside the object. Is this against the rules of
OOP?
Thanks
Michael
[To remove yourself from this list, or to change to digest mode, go to
http://www.penworks.com/lingo-l.cgi To post messages to the list, email
[email protected] (Problems, email [EMAIL PROTECTED]). Lingo-L is for
learning and helping with programming Lingo. Thanks!]
