You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flex.apache.org by "Lee Burrows (JIRA)" <ji...@apache.org> on 2014/03/11 23:55:43 UTC
[jira] [Comment Edited] (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:comment-tabpanel&focusedCommentId=13931097#comment-13931097 ]
Lee Burrows edited comment on FLEX-34135 at 3/11/14 10:55 PM:
--------------------------------------------------------------
If you dont want an up/downBorderSkin, set it to a transparent image rather than null. Flex relies on the borderSkin for mouse/touch interaction so it needs something to work with.
was (Author: leeburrows):
If you dont want an up/downBorderSkin, set it to a transparent image rather than null.
> 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)