Sanyam,
FYI, I had a similar problem with an accessory view that was crashing
until I added this line:
[dirDlg setAccessoryView:nil]; // On Snow Leopard, we need to do this
or we will subsequently crash.
-Michael Domino
Michael Domino | Identity Finder, LLC
250 West 57th St; Suite 2412 |
On Thu, Aug 11, 2011 at 10:35 PM, Sanyam Jain wrote:
> Still I was wondering, System should not have send some message to the
> delegate once the dialog is dismissed.
> That's strange behavior.
It's quite common, and something the documentation explicitly calls
out. See the last paragraph of "Us
dialog is dismissed.
That's strange behavior.
-Sanyam
From: Jens Alfke [mailto:j...@mooseyard.com]
Sent: Friday, August 12, 2011 9:20 AM
To: Sanyam Jain
Cc: cocoa-dev@lists.apple.com
Subject: Re: Application crashes after launching Open/Save dialogs
On Aug 8, 2011, at 2:34 AM, Sanyam Jain wr
On Aug 8, 2011, at 2:34 AM, Sanyam Jain wrote:
> Thread 0 Crashed: Dispatch queue: com.apple.main-thread
> 0 libobjc.A.dylib 0x92dd3eec objc_msgSend + 44
A crash in objc_msgsend means a message was sent to a bad object pointer.
Usually this means the object has a
Hi,
I have a Carbon based application, in which platform Open/save dialogs are
based on NSOpenPanel and NSSavePanel.
Since, am accessing Cocoa stuff inside Carbon app, I did NSApplicationLoad() as
suggested in one of Apple's document.
Whenever another dialog window is launched after the Open/Sa
