Be aware of your heirarchy and how the root view controller was added and how children are added.
In a situation where you have a root view controller, you can control all orientation from there - you can configure things so that orientation changes are or are-not passed down to child controllers. I pretty much ignore per-controller orientation issues, choosing instead to manage orientation through a root controller with flags defined to dictate to that root controller what orientations should or shouldn't allow, with automatic orientation change to supported orientations (based on the child controller setting those flags) whenever a controller is pushed or popped. Centralizing orientation management to a single point is much easier than trying to manage on a per-controller basis, just my 2 cents. However, if you have a root (again, depending on how you've set things up) and the root returns TRUE for all orientations, then the child may never have the opportunity to say otherwise. -- View this message in context: http://monotouch.2284126.n4.nabble.com/Having-1-ViewController-with-different-orientation-tp4656971p4656977.html Sent from the MonoTouch mailing list archive at Nabble.com. _______________________________________________ MonoTouch mailing list [email protected] http://lists.ximian.com/mailman/listinfo/monotouch
