I have an app I'm currently building that doesn't use the navigation controller but presents a number of views based on my own custom navigation.
I just have a function that handles "RemoveFromSuperView(outgoingviewhere)" and havent had any memory issues. Not sure this helps you at all, but figured it was worth mentioning. On Tue, Dec 6, 2011 at 9:12 AM, Mg <[email protected]> wrote: > Yes, I've seen the navigation controller before but I wasn't sure it would > fit my needs. I don't want the navigation controls. I am using some > customized controls for switching controllers. > > I just discovered Storyboards while looking at the Monotouch documentation > for IOS 5 and will probably go that route. However to help me understand > the > API better I would still appreciate it if someone had the answer to my > questions. I am concerned that calling PresentViewController on a new > instance every time the user flips screens may somehow keep a reference to > the calling controller causing an out of memory if the user changes screens > a lot. > > -- > View this message in context: > http://monotouch.2284126.n4.nabble.com/Switching-Views-tp4158757p4165028.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
