• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: cmd-q versus menu item quit
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: cmd-q versus menu item quit


  • Subject: Re: cmd-q versus menu item quit
  • From: Nick Zitzmann <email@hidden>
  • Date: Tue, 11 May 2004 12:15:17 -0600

On May 11, 2004, at 9:49 AM, Milton Sagen wrote:

When I quit via the key equivalent cmd-q all the objects associated with my window get dealloc'd such as an NSOutlineView, however, when I quit by selecting the quit menu item, even though my code "seems" to follow the same path, the objects don't get dealloc'd. Its as if they are never placed into an autorelease pool or the pool is itself never released. Has anybody else seen this and know how to get the quit menu item selection to behave the same as cmd-q?

I wouldn't worry about this too much, since the memory used by the task will be freed when the task exits careless of whether your application deallocates it or not.

Nick Zitzmann
<http://www.chronosnet.com/>
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.


References: 
 >cmd-q versus menu item quit (From: Milton Sagen <email@hidden>)

  • Prev by Date: Re: Problem Instantiating a Nib
  • Next by Date: Get a user friendly device name
  • Previous by thread: Re: cmd-q versus menu item quit
  • Next by thread: CFStringCreateWithCharacters and unicode ":" chars
  • Index(es):
    • Date
    • Thread