Re: "(Not Responding)" problems in Leopard
Re: "(Not Responding)" problems in Leopard
- Subject: Re: "(Not Responding)" problems in Leopard
- From: "Benjamin D. Rister" <email@hidden>
- Date: Tue, 13 Nov 2007 16:04:10 -0500
On Nov 13, 2007, at 3:44 PM, Uli Kusterer wrote:
Am 13.11.2007 um 04:36 schrieb Benjamin D. Rister:
No Carbon UI functions, though plenty of Carbon FS functions. No
call to NSApplicationLoad(), either--my understanding is that
that's only needed if you're trying to run a Carbon event loop and
use Cocoa.
Nope. NSApplicationLoad() is needed whenever you're calling AppKit
functions and you're not using NSApplicationMain().
Good to know, even if it doesn't seem to be the source of this
particular problem (per my later response to Nick and Sam).
Unfortunately, it seems that calling NSApplicationLoad() triggers a
series of dialogs complaining about the command line arguments I
passed to my tool. (This is even though it doesn't take argc/argv as
parameters--it must be getting them from somewhere else...) How does
one get NSApplicationLoad() to leave my arguments alone?
Best,
br
--
Benjamin D. Rister
President
Decimus Software, Inc.
http://www.decimus.net/
_______________________________________________
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