Apple

On 23 oct. 2008, at 14:05, Dalzhim Dalzhim wrote:

Hello Martin-Gilles,

in your NSView subclass interface builder implementation category, add the following method:

- (NSView *)ibDesignableContentView
{
retourne self;
}

You can also have a look at the documentation of this method if you wish to know what would be the effects of returning something else than self.

-Dalzhim

2008/10/23 Martin-Gilles Lavoie <email@hidden>
Hi folks.

Been a while since I couldn't answer my question by sifting through the web...

Up until now, we've been using an NSView subclass in our code, by setting the class name in Interface Builder Custom View object. This allows us to drop objects inside that view, such as buttons and whatnot, directly from within IB.

This NSView subclass is a complete layout management class and the number of possibilities in that code has piled up so much that I've decided it was time to create an IB plug-in to handle the many possible configuration of that subclass. Originally, everything was setup programatically within our awakeFromNib methods.

So, at this point, I have a complete IB plug-in with switches in the inspector that allows me to toggle some options of that class of ours. All fine and dandy.

However, for some reason, IB itself doesn't recognise our view as being a subclass of NSView and it wont let me drop objects inside it, like it does for recular custom views. The object is treated as a non-container.

What gives?

Martin-Gilles Lavoie | Senior software developer | 514.905.8658

Oracle - Macintosh Native Desktop Client, Beehive

600, boul. de Maisonneuve West, Suite 1900 | Montréal (Québec) H3A 3J2

References:
	>NSView subclass IB plug-ins conundrum (From: Martin-Gilles Lavoie <email@hidden>)
	>Re: NSView subclass IB plug-ins conundrum (From: "Dalzhim Dalzhim" <email@hidden>)