On 3/14/15, 10:36 AM, "jude" <flexcapaci...@gmail.com> wrote:
>I forgot about someone overriding setStyle. Right, so what about a method >like setStyleInState()? > >I'm thinking of supporting both styles and properties. > >If it's a style we create a mx.states.SetStyle and for properties we >create >a mx.states.SetAction and add to the state's overrides array. I could be wrong, but my current thinking is that if you are going to support both styles and properties, you don’t need any changes to StyleManager. State overrides are simply deferred calls to setStyle and various property setters. Even more important, as you return from that state back to some other state, the original style or property value gets applied. I don’t think you want to add and remove CSS Selectors. It will be too expensive and could affect other parts of the DOM. So, I think this feature should be independent of the CSS/StyleManager subsystem. I think what you really want is a way to store other overrides to be applied on state changes in various instances. -Alex
