Re: Impelmenting NSWindows95InterfaceStyle

[Fred Kiefer]

Matt Rice wrote:
> On Mon, Jan 19, 2009 at 3:14 AM, Pete French <pete@twisted.org.uk> wrote:
>>> I don't use mswindows very much, but it does not appear to be the sort
>>> of behavior you would expect from a windows application.
>>> I would expect use of NSWindows95InterfaceStyle to produce a menu in
>>> each windows and remove the main menu:
>> Does anybody here want to borrow my (ancient) copy of OpenStep for
>> Windows to take a look at how NeXT/Apple solved this ? Which is,
>> to the best of my recollection, precisely as described above.
>>
>> -pete.
>>
> 
> I have a copy here not all windows have them e.g. inspectors don't,
> I suspect that it only adds them to windows which respond yes to
> -canBecomeMainWindow, but didn't go through the trouble of verifying
> that

Sounds like the right condition to decide whether to add a menu. But
what should we do in the case, when there isn't a main window? Take for
example the GSTest application that doesn't display a window on startup.
Should we only have the context menu of the icon window?

> and if the window is too small to contain the menu it will stack the
> horizontal menus vertically kind of strangely
> e.g.
> 
> file menu2 menu3
> menu4 menu5