OK. Does anyone have any ideas, contributions or feature requests before I look into this further?
Do any of the compiler guys have any thoughts? I was going to ask Gordon Smith for his thoughts here but legend has it the only way to contact him is to type his name 3 times into command line at midnight during a full moon and you can ask him one question. If you ask two questions I hear you get the blue screen of death and the only way to restore your computer is to burn a floppy disk of HomeSite 5.0. On Mon, Mar 16, 2015 at 12:02 AM, Alex Harui <aha...@adobe.com> wrote: > > > On 3/15/15, 10:42 PM, "jude" <flexcapaci...@gmail.com> wrote: > > >OK so we would add an overrides array on UIComponent and when the state is > >changing check for any overrides and apply them? > > No idea exactly what to do here. I think there are several choices: > -Adding another property to UIComponent > -Adding a data structure(s) to the MXML document > -Adding a data structure(s) to the instance’s MXML document. > > The main downside of the first is that all UIComponent instances carry the > extra property regardless of whether they are actually involved in this > pseudo-states scheme. All three still have the challenge of when it is > the component’s skin and not the actual component that changes state. > > >Then in the compiler when > >we encounter a pseudo state attribute we add these to the instance's > >overrides array? > > For sure, the compiler needs to build up an array of overrides. > > -Alex > >
