You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flex.apache.org by "Maxime Fauberteau (JIRA)" <ji...@apache.org> on 2014/03/12 09:42:47 UTC

[jira] [Updated] (FLEX-34135) No way to affect null borderSkin to a Button

     [ https://issues.apache.org/jira/browse/FLEX-34135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Maxime Fauberteau updated FLEX-34135:
-------------------------------------

    Attachment: MyButtonSkin.as

Custom Button Skin, which can manage null up/downBorderSkin.

No error was thrown if null was assigned to up/downBorderSkin properties.

> 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
>         Attachments: MyButtonSkin.as
>
>
> 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)