I have a situation where a tap on a MT.Dialog.StringElement causes a PushViewController(view, true) to be called, to navigate to a new view. If I rapidly tap on the element then it seems multiple taps get queued up before the navigation is done. So I get several of my new view on the stack instead of just one. Nasty! I also get some warnings from the system (<Warning>: nested push animation can result in corrupted navigation bar). I've checked my code in the tapped event handler by logging out Environment.Stacktrace and my code is definitely not re-entrant (which means that the warning on nested pushes must be wrong, I wonder if it is generated if a new push happens before the last one has finished animating). I think now that there must be a bug in MT.Dialog or even in the TableViewController code. Has anyone come across this before? Surely I do not have to block multiple taps in my user code?!
Thanks for any insights... Felix -- View this message in context: http://monotouch.2284126.n4.nabble.com/Rapid-tapping-on-MT-Dialog-StringElement-causes-nested-navigation-pushes-tp4655287.html Sent from the MonoTouch mailing list archive at Nabble.com. _______________________________________________ MonoTouch mailing list [email protected] http://lists.ximian.com/mailman/listinfo/monotouch
