What's wrong with taking away Toolbar.Bounds.Height instead of 44 hardcoded?
René -----Ursprüngliche Nachricht----- Von: [email protected] [mailto:[email protected]] Im Auftrag von MilkyJoe Gesendet: Donnerstag, 27. Oktober 2011 21:28 An: [email protected] Betreff: [MonoTouch] View Frame: 460 != 416 - Hidden NavigationBar woes The first view in my app does not contain a nav bar. Well, it technically does, but it's hidden, as navigation is controlled via a series of buttons initially. The nav bar is made visible again in the view's ViewWillDisappear event, and this all works as intended. In the next view, I need to do some critical work in its ViewWillAppear event. I need to do it here as the form is only loaded once, but its content changes on each re-appearance, depending on which button was clicked in the previous view. The problem I have is that the view's frame size = 320x460, and not the 320x416 I was expecting (as the nav bar's hidden value has been set to false). From playing around, I can see that this is because the nav bar is not yet technically visible yet; deduced by the fact that the view's frame is 320x416 in the ViewDidAppear event. So... How should I fix this? Should I simply take 44 away from my calculations to allow for the navbar, or is there an altogether more elegant solution? I'd prefer to avoid such hard coding if possible. I'm sure I'm just missing something. Thanks -- View this message in context: http://monotouch.2284126.n4.nabble.com/View-Frame-460-416-Hidden-NavigationB ar-woes-tp3945733p3945733.html Sent from the MonoTouch mailing list archive at Nabble.com. _______________________________________________ MonoTouch mailing list [email protected] http://lists.ximian.com/mailman/listinfo/monotouch _______________________________________________ MonoTouch mailing list [email protected] http://lists.ximian.com/mailman/listinfo/monotouch
