Thanks Adam
Interesting feedback
So what do you do with the code in that function?
If my UIViewController is (pseudocode):
class MyUIVC
{
void ViewDidLoad()
{
ApplicationSingleton.Messages += MessageHandler;
}
void MessageHandler(s, e)
{
You should use ViewWillAppear() and ViewDidDisappear() instead.
René
Am 25.09.2012 um 10:51 schrieb slodge m...@slodge.com:
Thanks Adam
Interesting feedback
So what do you do with the code in that function?
If my UIViewController is (pseudocode):
class MyUIVC
{
void
On Sat, Sep 22, 2012 at 9:32 AM, Stuart Lodge m...@slodge.com wrote:
I'm interested in what to do without ViewDidUnload too.
Apple's recommendation is to handle memory warnings instead.
Rolf
Is there some other notification we should use to free up resources,
unsubscribe from events,
Thanks for the answer
I think my question now is a different one... I think maybe I was abusing
ViewDidUnload all along!
If I have a uiviewcontroller that attaches to an application singleton for
events - e.g. it attaches to a ChatServiceMonitor singleton and listens to
incoming Chat events -
I'm interested in what to do without ViewDidUnload too.
Is there some other notification we should use to free up resources,
unsubscribe from events, etc?
E.g does Dispose get called when a viewpoint roller gets popped off
the navigation stack? (Or when the memory warning arrives like
Just upgraded MT this morning to be able to support iOS 6. I'm seeing a
number of warnings when I build around a couple of deprecated methods in
iOS 6, specifically:
ViewDidUnload
ShouldAutorotateToInterfaceOrientation
I looked at Xamarin's doc on iOS 6
Very good questions! I was wondering about the ReleaseDesignerOutlets() as
well.
As far as ShouleAutorotateToInterfaceOrientation() is concerned: you can keep
that for now. That's what I understood from the relevant WWDC 2012 talks. Apple
is testing a new system but the old one is save to use
