Re: Document based application with that auto-new-doc behaviour
Re: Document based application with that auto-new-doc behaviour
- Subject: Re: Document based application with that auto-new-doc behaviour
- From: Gerben Wierda <email@hidden>
- Date: Mon, 25 Feb 2002 15:59:34 +0100
Thanks,
and what is the right place to put this method? Should I put it in my
WindowController subclass? When I do this, nothing happens, because
probably it is not the apps delegate. I do not understand (I am pretty
new at this) how to do this best. I am thinking about just making a
special class for just this purpose, instantiate it in IB and then set
the Apps delegate. But that seems to be taking the long route. So what
is the preferred way?
G
On Monday, February 25, 2002, at 03:27 , John Hvrnkvist wrote:
On Monday, February 25, 2002, at 03:15 PM, Gerben Wierda wrote:
I am writing a doc-based app that is passive, in the sense that it
uses a doc-based approach but the app itself cannot make new documents
(though it can change existing temporary non-essential document
settings).
Now, when I start the document, I get automatically a new document,
which is senseless because any new document needs to be opened. And
when all docs are closed and I reactivate the app, I get another new
document.
How do I stop this behaviour (which in this particular case is
absolutely silly)?
The application delegate is responsible for this.
- (BOOL)applicationShouldOpenUntitledFile:(NSApplication *)sender;
Regards,
John Hornkvist
--
ToastedMarshmallow, the perfect Cocoa companion
http://www.toastedmarshmallow.com
_______________________________________________
MacOSX-dev mailing list
email@hidden
http://www.omnigroup.com/mailman/listinfo/macosx-dev
_______________________________________________
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.