I could write a long drawn-out post about how we were creating event listeners today to set the enabled property of some of the button classes in our custom forms at work... blah blah blah.
Bottom line, UIComponent.as is missing this line:
[Event(name="enabledChanged", type="flash.events.Event")]
Give it a shot. Create a component that extends mx.core.Container (or, in our case, extends a custom component that extends Form.as) and create a function bindable to "enabledChanged". It won't work until you add the metadata somewhere.
That is all.
Tuesday, May 13, 2008
Saturday, May 10, 2008
Flex Builder / Eclipse tip du jour.
It's inevitable. You'll be debugging a Flex application, get an error and will need to look at a class, object, function or the like. Instead of scrolling up and down, or digging through directories, do the following:
Ctrl-click on the 'identifier' in question and you're in like Flynn.
Ctrl-click on the 'identifier' in question and you're in like Flynn.
Labels:
adobe flex
30th time is the charm?
Maybe it's a bad idea to start ANOTHER blog that may fall into the same ol' my-last-post-was-five-months-ago pit. But, what the hell...
Labels:
lame
Subscribe to:
Posts (Atom)