Richard Gaskin wrote:
What I discovered is that when you replace a whole set of properties en
masse like this, the setProp handler for the affected property set
doesn't trigger.
It'd be darned convenient if it did, but perhaps there's some reason why
it shouldn't.
Is this a bug or a feature?
More like not implemented, I think. SetProp catches individual
properties, but not whole sets. I don't suppose the engine actually
walks through each property when it does a mass replacement like that,
so no individual property events are sent.
--
Jacqueline Landman Gay | [email protected]
HyperActive Software | http://www.hyperactivesw.com
_______________________________________________
use-revolution mailing list
[email protected]
Please visit this url to subscribe, unsubscribe and manage your subscription
preferences:
http://lists.runrev.com/mailman/listinfo/use-revolution
