views:

1604

answers:

4

Having trouble getting the correct bounds for my iPad application when launching it in landscape mode. I have the proper keys set in my Info.plist file, and my view controllers launch properly in landscape (and portrait, natch).

In my applicationDidFinishLaunching: method I'm calling a selector after a 3 second delay, and that method makes a call to [[UIScreen applicationFrame], but it's returning me a portrait frame (ie height > width).

Does anyone know how to fix this? It smells like a bug to me (if so I'll file a radar), but if it's intended behaviour, where is it documented?

+2  A: 

This is as designed. You should query the size of your superview and adjust as necessary.

rpetrich
Could you explain why this is designed this way (or at least speculate). It seems illogical to me to give incorrect bounds for the screen if it has been rotated. The `superview` in question is my application's window (and I've tried using its frame as well to the same results).
jbrennan
The reason is that windows can be rotated independently of the screen. Example: when a portrait application launches a YouTube video, the main window remains portrait, but a landscape window animates over top of it. During the animation, should the device be considered portrait or landscape? (accelerometer orientation is separate from window orientation is separate from statusbar orientation)
rpetrich
I've noticed this as well, it's really weird. Thanks for the heads up.
JustinXXVII
My application's window is my superview in this case, and it's reporting Portrait bounds even though it is landscape. Frustrating. But I'll just have to use `[UIDevice orientation]` to swap the w+h if needed.
jbrennan
`-[UIDevice orientation]` should not be used for this purpose; `-[UIApplication statusBarOrientation]` should be used instead. `UIDeviceOrientation` has additional states that make no sense in this case: `UIDeviceOrientationUnknown`, `UIDeviceOrientationFaceUp` and `UIDeviceOrientationFaceDown`.
rpetrich
+1  A: 

When you are holding the iPad in landscape orientation and launch an app, the view controller initially sees bounds for a portrait view (even though orientation reports landscape). The view controller will then get a message to rotate to landscape orientation before it appears.

progrmr
+1  A: 

I never rely on [[UIScreen mainScreen] applicationFrame], especially during app launch.

When creating views in code, use the superview to set your frame.

If you're using xibs with "simulated interface elements" they will be correctly sized and everything will work great.

UINavigationController based apps

In the case of a UINavigationController based app, grab the frame directly from self.navigationController.view, don't try to use [self loadView] and self.view.superview. UINavigationController uses "hidden" subviews to do it's job--so the direct superview will not work.

UINavigationController is special because during app launch, the navigation controller resizes your views after loadView gets called. When autoresizing kicks in you end up with a small margin at the bottom of the screen.

Why not UIScreen

[[UIScreen mainScreen] applicationFrame] doesn't work reliably (especially during app launch in landscape). My experience is that the viewcontroller's interfaceOrientation property will not match the applicationFrame orientation.

bentford
A: 

I asked a similar question here: http://stackoverflow.com/questions/3972001/height-and-width-on-iphone-ipad

It may help you.

Jonathan