You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flex.apache.org by "OmPrakash Muppirala (JIRA)" <ji...@apache.org> on 2014/03/14 19:00:54 UTC

[jira] [Closed] (FLEX-34139) Missing 120DPI Skin References

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

OmPrakash Muppirala closed FLEX-34139.
--------------------------------------


Thanks for verifying the fix!

> Missing 120DPI Skin References
> ------------------------------
>
>                 Key: FLEX-34139
>                 URL: https://issues.apache.org/jira/browse/FLEX-34139
>             Project: Apache Flex
>          Issue Type: Bug
>          Components: Spark: ButtonBar
>    Affects Versions: Apache Flex 4.12.0
>            Reporter: Keith Lee
>            Assignee: OmPrakash Muppirala
>            Priority: Minor
>         Attachments: Screen Shot 2014-03-12 at 11.21.25 AM.png
>
>
> I started a discussion about this in the forum, but could not post a screen grab and wanted to make sure there's not a bug here. (http://apache-flex-users.2333346.n4.nabble.com/4-12-Application-Screen-Size-Issues-td5406.html) My desktop app is using mobile components and mobile theme. Upon upgrading to Flex 4.12, the previous applicationDPI setting of 160 no longer would work, so I removed it. The actual runtimeDPI is 120. Now some fonts are a little smaller, but I can live with that and adjust those accordingly. However, the TabbedNavigatorApplication's tab bar is skinned incorrectly. See attached screen grab. Upon investigation, the skin flex_4.12/frameworks/projects/mobiletheme/src/spark/skins/mobile/ButtonBarFirstButtonSkin.as does not have a entry for using 120DPI assets as it probably should, in order to look correctly on the desktop.



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