flex-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Alex Harui <aha...@adobe.com>
Subject Re: [DISCUSSION] MXML pseudo states suggestion
Date Tue, 10 Mar 2015 16:41:02 GMT
Maybe, but the way the code currently works is that the states are
declared in an MXML document and all state-dependent data is generated for
that same document.  While that state-dependent code does set styles and
properties on other instances declared in that document, some of those
instances are themselves MXML documents for which their state-dependent
code has already been generated, probably when it was compiled into a SWC.
 There’s no way to modify that generated code, so we need a different way
to determine when a state changes in a child object (yes, there events for
that) and then make the appropriate changes and figure out how to deal
with potential conflicts and what to do if the child object (or actually,
its skin) doesn’t support the state you think it does.


On 3/10/15, 4:53 AM, "Kessler CTR Mark J" <mark.kessler.ctr@usmc.mil>

>Is this something that could be accomplished by overriding the
>stateChanged[1] protected method since it's used for setting styles when
>the state changes?

View raw message