[
https://issues.apache.org/jira/browse/FLEX-34135?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13931874#comment-13931874
]
Lee Burrows commented on FLEX-34135:
------------------------------------
Confirmed that borderSkin not required for interaction (on sim at least).
I don't know whether allowing nulls by default would get much support - i
suspect not as it reverses expected behaviour so has the potential to cause
unwanted behaviour in existing codebases.
A more flexible solution would be to change borderClass and changeFXGSkin from
private to protected properties. Then you could extend ButtonSkin as you wish
without altering the behaviour of the SDK.
> 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)
