Hi Fréderic, In my opinion, you typically do not have to set applicationDPI or runtimeDPIProvider for Flex destop projects, if you leave them unset, then usually the applicationDPI and the runtimeDPI are both 120 when running on desktop os.
And if your app is running on desktop os with retina displays like the Retina Macbook Pro, then the AIR will automatically do the scaling for you by setting the Stage.contentsScaleFactor http://help.adobe.com/en_US/FlashPlatform/reference/actionscript/3/flash/display/Stage.html#contentsScaleFactor (You have to set <requestedDisplayResolution> to high in your -app.xml) Before AIR 22, the Stage.contentsScaleFactor only works on Mac OS, but the latest version of AIR 22 bring this feature to work on Windows as well, see the releason note of AIR 22, search for "Add HiDPI support for AIR desktop": http://labsdownload.adobe.com/pub/labs/flashruntimes/shared/air22_flashplayer22_releasenotes.pdf Therefore, I recommend that for all the Flex desktop projects, do not set applicationDPI or runtimeDPIProvider, leave them unset. The only thing you have to do is to set <requestedDisplayResolution> to high in your -app.xml, and use the latest AIR SDK, then the AIR will do the scaling for you. As for the Flex mobile projects, I recommend to set the applicationDPI to 160, and set the runtimeDPIProvider to your overrided class ONLY IF NECESSARY. Hope it helps. DarkStone 2016-05-20 在 2016-05-19 23:41:35，"Fréderic Cox" <coxfrede...@gmail.com> 写道： >I fixed my issue by not setting applicationDPI="160" but instead returning >160 always for a custom runtimeDPIProvider for desktop. This seems to work > >On Thu, May 19, 2016 at 5:28 PM, Fréderic Cox <coxfrede...@gmail.com> wrote: > >> I found the issue. It is only affecting the desktop preview so not an SDK >> issue but an issue with scaling. See >> https://issues.apache.org/jira/browse/FLEX-34653 >> >> I could easily fix this by setting applicationDPI in my desktop app but >> that causes the scaling bug as reported in >> https://issues.apache.org/jira/browse/FLEX-34653 >> >> So if you have a library project used in both mobile and desktop project >> then this issue can occur. >> >> On Wed, May 18, 2016 at 7:05 PM, Alex Harui <aha...@adobe.com> wrote: >> >>> Please file a JIRA issue and attach a simple test case including the >>> -app.xml file. >>> >>> Thanks, >>> -Alex >>> >>> On 5/18/16, 4:15 AM, "Fréderic Cox" <coxfrede...@gmail.com> wrote: >>> >>> >I only edited the AIR version since a compiler error showed up when I >>> >switched. No other changes made. >>> > >>> >On Tue, May 17, 2016 at 5:19 PM, Alex Harui <aha...@adobe.com> wrote: >>> > >>> >> Did you upgrade the -app.xml file? I'm wondering if there are settings >>> >>in >>> >> there affecting how it shows up. >>> >> >>> >> -Alex >>> >> >>> >> On 5/17/16, 3:23 AM, "Fréderic Cox" <coxfrede...@gmail.com> wrote: >>> >> >>> >> >MacBook Pro (15-inch, Early 2011) >>> >> > >>> >> >On Sun, May 15, 2016 at 7:44 AM, Alex Harui <aha...@adobe.com> wrote: >>> >> > >>> >> >> What kind of computer do you have? I'm wondering if it is Retina >>> >> >>display >>> >> >> support. >>> >> >> >>> >> >> -Alex >>> >> >> >>> >> >> On 5/14/16, 11:36 AM, "Fréderic Cox" <coxfrede...@gmail.com> wrote: >>> >> >> >>> >> >> >AIR desktop, but it is a library project which is included in AIR >>> >> >>desktop >>> >> >> >and AIR mobile. Both AIR mobile simulator and desktop show the >>> >>issue. >>> >> >>I'll >>> >> >> >try to find some time on monday to create a reproducable scenario >>> >>and >>> >> >>file >>> >> >> >a JIRA bug. Good to know that it is not an intended change as you >>> >> >>noted. >>> >> >> > >>> >> >> >On Sat, May 14, 2016 at 2:47 AM, Alex Harui <aha...@adobe.com> >>> >>wrote: >>> >> >> > >>> >> >> >> >>> >> >> >> >>> >> >> >> On 5/13/16, 5:41 PM, "Fréderic Cox" <coxfrede...@gmail.com> >>> wrote: >>> >> >> >> >>> >> >> >> >It is a bit of a guess but I'd say from 13 to 26. I fixed it by >>> >> >>setting >>> >> >> >> >s|TextInput to fontSize:13 in my CSS. Just found it odd that the >>> >> >> >>default >>> >> >> >> >has changed and I can't find any references about that in >>> release >>> >> >>note >>> >> >> >> >(maybe I'm overlooking it). If nobody else reported this I think >>> >> >>it's >>> >> >> >>not >>> >> >> >> >that big of a problem. >>> >> >> >> >>> >> >> >> I'm unaware of any such change to the SDK. Is this a web app, >>> air >>> >> >> >> desktop, or air mobile app? >>> >> >> >> >>> >> >> >> -Alex >>> >> >> >> >>> >> >> >> >>> >> >> >>> >> >> >>> >> >>> >> >>> >>> >>
