[FLEX-18397] Re-work disabled logic in Spark components

• Type: Task
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: Adobe Flex SDK Previous
• Component/s: Spark: General Component
• Environment: Affected OS(s): All OS Platforms; Language Found: English
• Assignee: Adobe JIRA
• Reporter: Adobe JIRA
• Created: 23/Mar/09 17:10
• Updated: 15/Apr/11 15:20
• Resolved: 19/May/09 23:44

Description

A couple of work items that came out of some hallway discussions regarding disabling Spark components:

1. Move the using of MouseShieldUtils.updateMouseShield from FxContainerBase up to FxComponent
2. Investigate getting rid of using a mouse shield at all
-In Halo we used a mouseShield to block mouse events AND to dim the component since we couldn't fade text
-In Spark, we can fade text, so the skin takes care of the dimming. To block mouse events I don't think we actually have to create a mouseShield sprite, instead we can set mouseEnabled & mouseChildren to false and be set.
3. If we do #2, look into getting rid of the updateMouseShield() call in updateDisplayList in FxComponent and instead override the enabled setter to toggle mouseEnabled/mouseChildren appropriately.