As Hamlet said, There are more things in heaven and Earth, Horatio, Than are dreamt of in your philosophy.
I may have a damn good reason for doing this...such as being able to define the property to change as a symbol in a GDPL, etc. etc. And, as I was asking about sprite-object properties, the script attached to the sprite-object IS the right place to be mucking with the properties of an 'object'.
I wasn't even addressing it to a specific person, I was knee-JERK reacting to the 'that's not OOP!' reactions. Sometimes the atmosphere of helpful advice which can't bother to answer the question gets a little thick, even though none of us really needs to be nice and helpful and answer people's questions at all.
"Do you have a phone, I need to call 911, there's been a car accident."
Imagine Edie McClurg, the nosey-neighbor from Small Wonder ( http://imdb.com/name/nm0566052/ ) saying this part:
"Oh, yes I do. You know, people do drive much too fast in those automobiles they're always zooming around these days, going hither and thither far too fast and disturbing the cows in the field with their fast engine going-ons, and wasting all those resources and creating all that smog, just look at that dirty yellow sky, and risking the lives of stalwart police officers like my husband..."
I'm sorry. Yes, it's offensive. Yes, a tremendous amount of the problem must be the way I asked the question, since I had to clarify at least once.
(And as a long time director programmer, feeling a little patronized, though I can't blame anyone for my own ego-problems.)
--------------- x = #fontsize put memberObject.getprop(x) works
x = #pScriptProperty put scriptObject.getProp(x) works
x = #blend put spriteObject.getProp(x) crashes.
I know I can (1) format the spriteObject one with do's or (2) have a LUT via case statements. And daniel plaenitz added (3) the value() statement. That may be the one I was missing...
x = #blend (1) do "put spriteObject."&x
(2) case x of #blend: put spriteObject.blend #locH: put spriteObject.locH #locV: put spriteObject.locV #color: put spriteObject.color otherwise --get tired of making LUT's nothing end case
(3)
put value("spriteObject." & x)Are there any more? ---------------
I should have waited patiently for a possible answer instead of flying off and attacking the people trying to answer my question.
I'm sorry.
roymeo "You shouldn't be doing that in Flash..." or is it "You shouldn't be doing that in Director..."?
At 04:32 PM 2/20/2004, you wrote:
On Friday, February 20, 2004, at 04:02 PM, roymeo wrote:
Yes, OOP-Nazi, you are right.
Me? I'm hardly that. Just seemed to me that asking the sprite to tell you what you wanted to know was better in this case. Not to mention that *you* were the one who said - "that's the way object stuff works."
Whatever. Good luck with it. -- Troy RPSystems, Ltd. http://www.rpsystems.net
[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!]
---------- roymeo(AT)brokenoffcarantenna.com ---------- i used to love you back when you wrote poetry
[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!]
