Skip to main content
Participant
June 27, 2012
Question

Stage has wrong fullScreen sizes when launched in adl

  • June 27, 2012
  • 2 replies
  • 801 views

Actually this problem only occurs when these two properties are set in the descriptor file:

<aspectRatio>landscape</aspectRatio>

<autoOrients>false</autoOrients>

As aspected the stage has the following correct properties:

stage.autoOrients  –>  false

stage.deviceOrientation  –>  rotatedLeft

But the values for the fullScreen size values are (iPad screen size):

stage.fullScreenHeight  –>  1024

stage.fullScreenWidth  –>  768

So although the deviceOrientation is set to a landscape aspect ratio, the values for fullScreenWidth and fullScreenHeight do not reflect this. The odd thing is that this does not apply when the same application is launched on the device – in this case iPad3 (normal resolution). Then the values are correct:

stage.fullScreenHeight  –>  768

stage.fullScreenWidth  –>  1024

When I launch adl I set the following two properties:

-profile extendedMobileDevice -screensize iPad

It seems that although the descriptor file sets the aspect ratio to landscape adl sets the stage values initially to the default/normal aspect ratio in portrait orientation. It gets really weird when I set the screen sizes explicitly like this:

-profile extendedMobileDevice -screensize 1024x768:1024x768

Then window adl launches is in portrait orientation but the fullScreen sizes are correct! I did a very quick search online but could find anything regarding this issue. Is it known? Does a bug report already exist?

I should add that I'm running on OS X 10.7.4 with the latest Air SDK added to the latest Flex SDK (Flex 4.6.0.23201B, Air 3.3). I haven't tested other Air versions and neither did I run any tests on a PC.

This topic has been closed for replies.

2 replies

chris.campbell
Legend
June 27, 2012

Could you open a bug for this at bugbase.adobe.com?  I'll also forward this to the iOS team for their review.

Thanks,

Chris

dbeermannAuthor
Participant
June 27, 2012

Hi Chris,

just opened a bug: https://bugbase.adobe.com/index.cfm?event=bug&id=3225490

Thanks,

David