Re: application:openFile:

[Rob Burns]

Ok, thanks for explaining that. An easy fix for non-NSDocument based 
applications. I think there are still problems, though. In the case where you 
don't want the app activated, but want the file open, the file doesn't get 
opened at all.  I seem to remember something about this having to do with focus 
issues. Could be wrong again.

It also doesn't seem that NSDocument based apps work either. I did some looking 
for documentation on NSDocument applications, and found this for 
NSDocumentController.

As the application delegate, it saves and closes documents when
applications are terminated and it responds to NSWorkspace methods when
documents are opened or printed from the workspace.

I think Ink is an NSDocument based app. It uses a sublclass of NSDocument. But 
it looks like it gets it a little bit wrong. as it has its own custom 
application delegate, that isn't a subclass of NSDocumentController. So its 
probably not the best for testing NSDocumentController stuff. CodeEditor on the 
other hand does have a subclass of NSDocumentController as its app delegate, 
which, I think, is better for testing.  In any case both of them behave the 
samel. you can open one file. but trying to open another results in the app 
coming to the foreground, without the additional file open. If you close the 
first one, you can open another.

Am I understanding that more or less correctly? Or am I still missing something?

Rob

On 2003-04-27 22:05:48 +0700 Alexander Malmberg <alexander@malmberg.org> wrote:

> Applications (except NSDocument-based apps) that want to activate
> themselves when opening files should do it themselves, so it sounds like
> Ink is doing the right thing.
>
> - Alexander Malmberg
>
>
> _______________________________________________
> Discuss-gnustep mailing list
> Discuss-gnustep@gnu.org
> http://mail.gnu.org/mailman/listinfo/discuss-gnustep