Re: *** -[NSSavePanel _blocksActionWhenModal:]: message sent to deallocated instance 0x15a05e50
Re: *** -[NSSavePanel _blocksActionWhenModal:]: message sent to deallocated instance 0x15a05e50
- Subject: Re: *** -[NSSavePanel _blocksActionWhenModal:]: message sent to deallocated instance 0x15a05e50
- From: Graham Cox <email@hidden>
- Date: Mon, 25 Aug 2008 15:50:48 +1000
On 25 Aug 2008, at 11:09 am, Kyle Sluder wrote:
On Sun, Aug 24, 2008 at 6:03 PM, Cate Tony <email@hidden> wrote:
If I put a retain on the panel, the error stops, but isn't it now
leaking?
No. You took ownership of the NSSavePanel when you created it by
using a convenience constructor. You must retain it, and release it
when you're done with it.
Except that the NSSavePanel docs state:
"An NSSavePanel object is a singleton: when you request a Save panel,
NSSavePanel tries to reuse an existing Save panel rather than create a
new one"
I don't usually retain it and have never seen this crash... but I also
see it says TRIES to... so maybe it creates new instances sometimes
depending on the parameters. It would be good to have a bit more
certainty in the docs on this one - is it a singleton or not, and if
not, under what circumstances exactly is that?
cheers, Graham
_______________________________________________
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