Bug 7363 - Incorrect LandscapeRight Dimensions
Summary: Incorrect LandscapeRight Dimensions
Status: RESOLVED NORESPONSE
Alias: None
Product: iOS
Classification: Xamarin
Component: General ()
Version: 6.0.x
Hardware: Macintosh Mac OS
: --- normal
Target Milestone: Untriaged
Assignee: Bugzilla
URL:
Depends on:
Blocks:
 
Reported: 2012-09-20 18:27 UTC by Pierce Boggan [MSFT]
Modified: 2013-12-05 18:34 UTC (History)
4 users (show)

Tags:
Is this bug a regression?: ---
Last known good build:

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and Mono organizations on GitHub to continue tracking issues. Bugzilla will remain available for reference in read-only mode. We will continue to work on open Bugzilla bugs, copy them to the new locations as needed for follow-up, and add the new items under Related Links.

Our sincere thanks to everyone who has contributed on this bug tracker over the years. Thanks also for your understanding as we make these adjustments and improvements for the future.


Please create a new report on Developer Community or GitHub with your current version information, steps to reproduce, and relevant error messages or log files if you are hitting an issue that looks similar to this resolved bug and you do not yet see a matching new report.

Related Links:
Status:
RESOLVED NORESPONSE

Description Pierce Boggan [MSFT] 2012-09-20 18:27:33 UTC
When application starts up using UIInterfaceOrientation.LandscapeRight, the dimensions are not displaying properly. 

User's description:
-If the app starts running in Portrait mode, then rotates to Landscape mode, the Landscape dimensions ARE correct.
-If the app starts running in Landscape mode, dimensions are incorrect. If app rotates to portrait, dimensions ARE correct.

Below is the log of the dimensions when the app starts up in Landscape mode.

Note: The user experienced this issue AFTER upgrading to MT 6.0.0.

Startup on Landscape Right:
2012-09-20 17:03:21.418 Test[14577:1507] Type: UIScreen.MainScreen.CurrentMode.Size
2012-09-20 17:03:21.425 Test[14577:1507] Width: 768
2012-09-20 17:03:21.426 Test[14577:1507] Height: 1024
2012-09-20 17:03:21.426 Test[14577:1507] Type: View.Frame.Size
2012-09-20 17:03:21.427 Test[14577:1507] Width: 768
2012-09-20 17:03:21.428 Test[14577:1507] Height: 1004
Comment 1 Sebastien Pouliot 2012-09-20 20:20:49 UTC
We'll need a test case. I have (ipad) apps that start correctly on both orientation, they worked in iOS5 before and did not need any change for iOS6 (and MT6).
Comment 2 Pierce Boggan [MSFT] 2012-09-21 14:55:39 UTC
As far as I'm aware, the issue at hand isn't with the app starting with the correct orientation, it's a problem with the actual view size properties. Size is displaying as the Portrait mode dimensions, when it should be Landscape mode dimensions. Note this is only when it starts up in Landscape.
Comment 3 Sebastien Pouliot 2012-09-21 20:28:13 UTC
I started my app, rebuilt with iOS6, from both landscape position and the dimensions were identical both times.

2012-09-21 20:25:21.535 X[3102:907] UIScreen.MainScreen.CurrentMode.Size {Width=2048, Height=1536}

2012-09-21 20:26:09.615 X[3116:907] UIScreen.MainScreen.CurrentMode.Size {Width=2048, Height=1536}

Test case needed!
Comment 4 AndyW 2012-09-24 11:46:00 UTC
I've also run into this problem with my app. I've created a test case here:

https://dl.dropbox.com/u/10852937/TestLandscape.zip

As you can see the Orientation is Landscape but the Width, Height and Center are wrong for that Orientation.

2012-09-24 16:42:59.004 TestLandscape[5878:1807] Orientation: LandscapeRight
2012-09-24 16:42:59.014 TestLandscape[5878:1807] Frame: {X=0,Y=0,Width=748,Height=1024}
2012-09-24 16:42:59.018 TestLandscape[5878:1807] Center: {X=374, Y=512}

Hope this helps

Andy
Comment 5 Sebastien Pouliot 2012-09-24 19:44:37 UTC
Andy, I think what you're looking for is the Bounds property *after* it has been displayer (e.g. after ViewDidAppear).
Comment 6 PJ 2013-11-19 17:04:47 UTC
This bug has been in the NEEDINFO state with no changes for the last 90 days. Can we put this back into the NEW or CONFIRMED state, or are we still awaiting response?

If there is no change in the status of this bug over the next two weeks, this bug will be marked as NORESPONSE.
Comment 7 PJ 2013-12-05 18:34:58 UTC
This bug has not been changed from the NEEDINFO state since my previous comment, marking as RESOLVED NORESPONSE.

Please feel free to REOPEN this bug at any time if you are still experiencing the issue. Please add the requested information and set the bug back to the NEW (or CONFIRMED) state.