flex-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Maxime Fauberteau (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FLEX-34135) No way to affect null borderSkin to a Button
Date Wed, 12 Mar 2014 08:38:44 GMT

    [ https://issues.apache.org/jira/browse/FLEX-34135?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13931537#comment-13931537
] 

Maxime Fauberteau commented on FLEX-34135:
------------------------------------------

Are you sure of that?
I did a test with a custom skin button, that is a copy of spark.skins.mobile.ButtonSkin, where
I added different "non-null" tests, and it works with null up/downBorderSkin. Mouse and touch
interactions work perfectly, probably because it's managed by ButtonSkin and not by up/downBorderSkin...

Maybe I'm wrong...

> No way to affect null borderSkin to a Button
> --------------------------------------------
>
>                 Key: FLEX-34135
>                 URL: https://issues.apache.org/jira/browse/FLEX-34135
>             Project: Apache Flex
>          Issue Type: Wish
>          Components: Mobile: Button Skin
>            Reporter: Maxime Fauberteau
>            Priority: Minor
>
> It seems that it could be impossible to assign a "null" skin to properties upBorderSkin
and downBorderSkin.
> If you try to do that, an error was thrown in this function :
> override protected function commitCurrentState():void
> {   
>         super.commitCurrentState();
>         
>         borderClass = getBorderClassForCurrentState();
>         
>         if (!(_border is borderClass))
>             changeFXGSkin = true;
>         
>         // update borderClass and background
>         invalidateDisplayList();
> }
> Can you add a "non-null" test to be safer ?
> Furthermore, it is the only place where the "non-null" test isn't done...



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message