Lists

Open Menu Close Menu

Terms and Conditions
Lists hosted on this site
Email the Postmaster
Tips for posting to public mailing lists

Re: NSWindowController maddness!

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: NSWindowController maddness!

Subject: Re: NSWindowController maddness!
From: "M. Uli Kusterer" <email@hidden>
Date: Tue, 9 Nov 2004 18:28:38 +0100

At 11:20 Uhr -0600 09.11.2004, Todd Freese wrote:

Can I assumed that if the controller was indeed released, that the pointer
to it will point to nil? Or should I be setting the pointer to nil myself?

No, the pointer won't be set to nil. If you want to find out whether it's been released, change its -dealloc method to NSLog() something and call the inherited method. That will tell you whether it went away.

You may want to read my article on how memory management works, maybe that'll help:

 <http://www.zathras.de/angelweb/howmemorymanagementworks.htm>
--
Cheers,
M. Uli Kusterer
------------------------------------------------------------
       "The Witnesses of TeachText are everywhere..."
                   http://www.zathras.de
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden



References:  
  >Re: NSWindowController maddness! (From: Todd Freese <email@hidden>)




Prev by Date:
Re: Why does NSBundle's load fail?

Next by Date:
Re: making tableview non sortable

Previous by thread:
Re: NSWindowController maddness!

Next by thread:
Re: NSWindowController maddness!

Index(es):

Date
Thread