Archive for May, 2009

Is that component really disabled?

When disabling a container, while its children will appear to be disabled, they are not disabled in the manner that they would be if you set the enabled property to false on them directly. When a container is disabled, it will no longer respond to input from the mouse or keyboard and will apply an alpha to itself and all of its contents. However, the children of the container will not in fact be disabled and so they can still be changed programmatically. For example, if a Panel contains a NumericStepper, and outside of the Panel a Button increments and decrements the NumericStepper’s value, disabling the Panel will not prevent the Button outside of the Panel from changing the value of the NumericStepper. Disabling a container is only intended to prevent direct user interaction with the container (and its children) and to modify the appearance in order to indicate that the container is in fact disabled.


Welcome to the FlexReport! I started this blog to provide an additional resource that the Flex community can use to learn about the framework. I plan to use this site as a mechanism to discuss ideas and lessons I’ve learned working with Flex and to hopefully provide some new insight into how Spark and Halo components work (as well as how they don’t work). My goal is to focus on some of the less intuitive use-cases and behaviors associated with the SDK so that readers can save time figuring out how various components work and instead focus on other aspects of their Flex projects.

A brief note about me – my name is Jacob; I am a member of the Flex SDK QA team in San Francisco and have been with Adobe since June of 2008.