Hi,
MX (Halo) was discontinued long time ago.
The 'enabled' implementation of the Spark SkinnableComponent is correct, no
need to change, it's better this way, because developers can explicitly set the
values of the mouseChildren and mouseEnabled for their CustomSkin.mxml.
If you do want to change it, you can subclass the SkinnableComponent, and
override the public function set enabled(value:Boolean):void to whatever you
want it to be.
DarkStone
2014-07-17
At 2014-07-17 05:51:46, João Fernandes" <joaopedromartinsfernan...@gmail.com>
wrote:
>Hi, something that has bugging me is that skinnable components behave
>differently from mx conter part when the object has enabled = false.
>In MX all components still respond to mouseEvents while skinnable won't
>because at the skinnableComponent level we have this
>
> override public function set enabled(value:Boolean):void
> {
> super.enabled = value;
> invalidateSkinState();
>
> // If enabled, reset the mouseChildren, mouseEnabled to the
>previously
> // set explicit value, otherwise disable mouse interaction.
> super.mouseChildren = value ? _explicitMouseChildren : false;
> super.mouseEnabled = value ? _explicitMouseEnabled : false;
> }
>
>I plan to implement a similar mx behavior but keeping the current behavior
>as the default.
>
>Before I start doing anything, is there any reason for this difference in
>behavior?
>
>--
>
>João Fernandes
