On Mar 8, 2008, at 8:27 AM, Quincey Morris wrote:
On Mar 8, 2008, at 06:54, Trygve Inda wrote:
IB3 has added an NSApplication object. How does this work... It
seems if my
AppController is still the delegate of the File's Owner that the
specific
instance of NSApplication is not needed
On Sat, Mar 8, 2008 at 8:57 PM, Quincey Morris
<[EMAIL PROTECTED]> wrote:
> I wonder if there's any legal scenario for an application to create
> two NSApplication (or subclass) objects, in particular to create two
> in such a way that the non-main one needed to load its own nib file.
No, becau
On Mar 8, 2008, at 10:54, Kyle Sluder wrote:
IB doesn't know for sure that the file's owner of the main nib is in
fact the shared NSApplication instance. You could be doing some wonky
stuff instead. The only way that IB could possibly know is if it
performed static analysis. So rather than b
On Sat, Mar 8, 2008 at 11:27 AM, Quincey Morris
<[EMAIL PROTECTED]> wrote:
> In a main menu nib, Application and File's Owner will be placeholders
> for the same object. Interestingly, IB doesn't seem to be smart enough
> to realize that they must be the same object, so setting the outlets
> of
NSApplication shared instance is now available in all NIB files in
IB3. It's there for convenience.
File's owner is the object loading the nib. In general, it is NSApp
only for MainMenu.nib (the first NIB to be loaded). In that NIB, both
objects designate the same instance.
--
Julien
Sen
On Mar 8, 2008, at 06:54, Trygve Inda wrote:
IB3 has added an NSApplication object. How does this work... It
seems if my
AppController is still the delegate of the File's Owner that the
specific
instance of NSApplication is not needed Since it is created at
run time
anyway.
It's a p
In IB 2 there was only a File's Owner and First Responder and one typically
made an AppController object as a subclass of NSObject and made it a
delegate of File's Owner.
IB3 has added an NSApplication object. How does this work... It seems if my
AppController is still the delegate of the File's O