• 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: EXC_BAD_ACCESS when calling NSOpenPanel
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: EXC_BAD_ACCESS when calling NSOpenPanel


  • Subject: Re: EXC_BAD_ACCESS when calling NSOpenPanel
  • From: Jens Alfke <email@hidden>
  • Date: Wed, 25 Nov 2009 17:11:07 -0800

On Nov 25, 2009, at 3:25 PM, Ken Thomases wrote:

> You haven't retained this panel.  If you want this object to live beyond the current autorelease context, you need to retain it. (Note that not retaining doesn't guarantee that it _will_ be released at the end of the autorelease context, just that it might.)

It's a window, so it'll be retained by AppKit as long as it's open. I've never seen any code using open/save panels that bothers to retain the objects.

—Jens_______________________________________________

Cocoa-dev mailing list (email@hidden)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:

This email sent to email@hidden

References: 
 >EXC_BAD_ACCESS when calling NSOpenPanel (From: Darren Wheatley <email@hidden>)
 >Re: EXC_BAD_ACCESS when calling NSOpenPanel (From: Ken Thomases <email@hidden>)

  • Prev by Date: Core Data and +[NSExpression expressionForFunction:...]
  • Next by Date: Looking for PCI card with IR transmitter ports and OS X drivers
  • Previous by thread: Re: EXC_BAD_ACCESS when calling NSOpenPanel
  • Next by thread: mySQL libs and an apology...
  • Index(es):
    • Date
    • Thread