you're telling the flash player when to fire bindings on the listeners for
your property. Sure, if you don't want to use their binding mechanism you
could hook it all up yourself, but you'd have to make all your classes
explicitly listen for the custom events you're firing. If you specify a
custom Binding event for a property, you're just controlling when Flex will
update everyone who's bound to that property, so the binding {} squiggly
braces work in MXML and BindingUtils. So specify the event you want Bindings
to fire on, then dispatch that event anywhere in your class to trigger
anyone bound to that property and you're good to go. Also handy to provider
a getter for calculated values and trigger the binding anytime something
affecting the calculation has changed.On Fri, Apr 25, 2008 at 12:35 PM, Troy Gilbert <[EMAIL PROTECTED]> wrote: > > Ah, so if specify the event name, then "bindable" truly is just > > metadata, no code-generation, right? That sounds like the info I was > > looking for... > > Which leads me to think, what exactly is bindable doing for me at that > point? If I'm firing the event (and thus creating it), is the metadata > just helping the compiler issue a warning about bindings not firing > for given properties? Is there anything else I'm getting? Do I get > code-complete on the bindable event or anything like that (like I'd > get if I added an Event metadata)? > > Troy. > >
