A common problem I've noticed, even on the SDK team, was when you have one property dependent on another property (or a set of other properties), and you need that property to be Bindable. For example, in spark.components.VideoPlayer, volume is dependent on the videoDisplay.volume property. Usually to make such a property bindable, you add an event listener to know when your dependent property changes. In this case, if you check out VideoPlayer.partAdded(), you can see code like that. However, when I started using the presentation model pattern, this issue seemed to keep coming up quite frequently.
|
|
Scooped by
Nicolas Bousquet
onto Everything about Flash June 20, 2011 6:15 AM
|
No comment yet.
Sign up to comment
Your new post is loading...