> In that case, the bindable("someEvent') tells the binding code which event
> to listen for before updating anything depending on that property.Gotcha. Good to know about the code generation. Here's a question for ya: If you let Flex fill-in all the binding code (if you don't specify an event name), it dispatches a PropertyChangeEvent with all the details (property name, oldValue, newValue). If you specify the event name, it doesn't seem to require that the event dispatch actually be a PropertyChangeEvent. Ergo, I'm guessing the binding the mechanism only listens for a particular named event and doesn't actually care about the data of that event, i.e. the property name, oldValue, newValue? Obviously, those details are useful for more complex situations where you're listening for a specific property change, but I'm guessing the binding mechanism is just needing a trigger (which basically tells the binder to get the property value again)? Troy.
