Heh heh. Been there, done that. I think that's why setting the property to *NOT* the property is a better way to go. Less moving parts.
I think of properties as variables that remain persistent and are global by nature. Obviously they are a different kind of animal, as anyone on this list will be quick to point out, but from a programmatical point of view it serves me well. One other advantage to accessing a property directly is I can tell any time I want what is in the property. With Variables, I have to be running a script, either in a script or in the message box. That bit of wisdom and $2.40 will get you a venti brew with 5 shots of your favorite syrup at your local Starbucks. Bob On Mar 2, 2010, at 1:00 PM, Andrew Kluthe wrote: > > :-P > > doh, that explains why after fixing it, the button would always toggle > false. > -- > View this message in context: > http://n4.nabble.com/Scripting-systemWindow-tp1575500p1575708.html > Sent from the Revolution - User mailing list archive at Nabble.com. > _______________________________________________ > 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 _______________________________________________ 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
