[
https://issues.apache.org/jira/browse/FLEX-34688?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14248459#comment-14248459
]
Hugo Ferreira commented on FLEX-34688:
--------------------------------------
I don't know if there is a JIRA ticket.
This problem probably is already solved or there is already a workaround for it.
This problem exists since the Adobe Flex 4.6.0.
The first Flex Mobile Version (4.5.0) introduced a lot of flex mobile
components including TextInput.
The second Flex Mobile Version (4.5.1) added rounded corners to TextInput thru
a mobile skin out-of-the-box.
The third and last Adobe Flex Mobile Version (4.6.0) removed that beautiful
rounded skin.
The workaround is to apply to skin again thru the skinClass in the TextInput
construtor (this is probably not needed anymore nowadays but with the new
Android and iOS skins I have the intention to remove this older skin anyway and
any time).
> New Android skin does not work at all with Flex Mobile libraries
> ----------------------------------------------------------------
>
> Key: FLEX-34688
> URL: https://issues.apache.org/jira/browse/FLEX-34688
> Project: Apache Flex
> Issue Type: Bug
> Affects Versions: Apache Flex 4.14.0
> Environment: MacOSX AIR Simulator and Android real device
> Reporter: Hugo Ferreira
>
> I tested the new Apache Flex 4.14.0 mobile skins successful with a test
> project.
> Now, I tried to apply in a real application and I never use flex mobile
> directly from the Flex framework. Instead I use a Flex Mobile Library to
> extend all Flex mobile components that I need (to customize if needed).
> What I saw is that if I use a flex mobile component directly from the Apache
> Flex framework, then the new Android skin is successfully applied but if I
> use directly from a flex mobile library (and this mobile library directly
> from the Apache Flex), then, is applied the older skin in AIR simulator but
> also in a real Android device (I already checked the library to use the new
> Apache Flex 4.14.0 but this didn't solved the problem).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
