[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: NSWindowController should be a NSResponder
From: |
David Ayers |
Subject: |
Re: NSWindowController should be a NSResponder |
Date: |
Thu, 23 Oct 2008 09:40:11 +0000 |
Am Donnerstag, den 23.10.2008, 10:27 +0200 schrieb Fred Kiefer:
> Committed. Thank you for this patch!
>
> Fred
>
> PS: Only gui applications using a custom subclass of NSWindowController
> need to be recompiled.
(... and categories...)
The change is good and correct for trunk but what's more interesting ist
that you probably have to consider NSCoding implication for non-keyed
un/archivers... this seems non trivial to fix.
Cheers,
David
> Wolfgang Lux wrote:
> > This patch fixes an issue that has bugged me already for quite a
> > while -- NSWindowController should be a subclass of NSResponder and
> > be part of the responder chain. Thus, window controllers automatically
> > receive event and action messages without having to make them delegates
> > of their windows (which does not help for event messages, anyway). This
> > has been the case in OS X for a very long time (AFAIR, one of the
> > developer releases), but never made it into GNUstep (though, curiously,
> > Gorm's class browser considers NSWindowController a subclass of
> > NSResponder already). So here is the patch to make this work.
> >
> > Note that the patch changes the object layout of NSWindowController
> > and its subclasses, so it will be necessary to recompile all (gui)
> > applications after applying this patch.
> >
>
>
> _______________________________________________
> Discuss-gnustep mailing list
> Discuss-gnustep@gnu.org
> http://lists.gnu.org/mailman/listinfo/discuss-gnustep