Geoff, This definitely shows me the 'best' use of a setProp. Thank you. I would say for me the guidelines for best use of a setProp are: 1.) Where I have an object with my own properties that get set often.
2.) Where I might have more than one control over those properties from different scripts/objects.
3.) Where I wish to keep the attributes and settings of that object 'with' that object.
Because of this I have two projects where one is not a best use of the setProp but the other 'should' have been done with setProp or 'would' be more 'travel-able' with setProp.
NOTE: I did 'break' this stack and was not paying attention to 'how' I did it. It seems i end up with two groups and can't find background errors. When I get some time I will go back to a fresh stack and step through with an eye toward errors. I will get back to you on them.
Thank you very much for this, Tom On Apr 13, 2006, at 8:59 AM, Geoff Canyon wrote:
go stack url "http://www.inspiredlogic.com/windowshade/ windowshadecc.rev"
Thomas J McGrath III [EMAIL PROTECTED] Lazy River Software™ - http://www.lazyriversoftware.com Lazy River Metal Art™ - http://www.lazyriversoftware.com/metal.html Meeting Wear™ - http://www.cafepress.com/meetingwear Semantic Compaction Systems - http://www.minspeak.com SCIconics, LLC - http://www.sciconics.com/sciindex.html _______________________________________________ use-revolution mailing list use-revolution@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-revolution
