Hi all,
I have an app with 3 primary views, 2 of which are table views
when in portrait mode, but display as full screen coverflow style in
landscape mode. I originally created a 3rd table view to serve as the
initial view as a way to get to the 3 main views with the intent I
would migrate the whole thing to use a UITabBarController. The basic
design was a UINavigationController as the top level view controller,
which was init'd with the 3rd table view. The controllers for my other
views would be pushed/pop on/off the controller stack based on row
selections for the top table view. For example, if I was viewing in
portrait mode and turned the device to landscape I would push the view
controller for my coverflow view onto the stack, hide the naviagtion
and status bars and that was all there was to it. That all worked
beautifully, but now I'm trying to convert the interface to use a
UITabBarController and running into problems getting rotation events
such as willRotateToInterfaceOrientation or
didRotateToInterfaceOrientation.
I've looked at a number of samples, including the MoviePlayer, and
it seems possible, although none of the samples seem to be doing quite
the same thing. For instance, the MoviePlayer switches based upon a
tap, not an orientation change. Am I just missing something
fundamental to UITabBarController behavior? Would an approach that
incorporates a UITabBar as an additional view beneath my table views
work better? It would mean managing the UITabBar myself, but I have
every reason to believe that I would get orientation change callbacks.
Anyone have any ideas what I'm missing here?
Bob
_______________________________________________
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com
This email sent to arch...@mail-archive.com
