
Signature
Michael Ash
Rogue Amoeba Software
> Toolbars mainly give you customizability. The user can show or hide it,
> can make the icons big or small or none, can rearrange the items or
> choose which ones are visible. It sounds to me like none of this will
> apply to you.
Not really. The application has a "standard" mode where all the windows
are ordinary windows, movable, resizeable, customizable et. But there's
also a Kiosk mode where everything should look and work normally,
without all the customizing stuff.
> In that case, is there really any difference between a
> true NSToolbar and a region of the window which happens to contain a
> bunch of borderless NSButtons with images set?
Customizing is not all a toolbar is good for. There's also the look and
feel, which is important. Reprogramming the toolbar would cause problems
whenever Apple redesignes their GUI.
Also a NSToolbar already has all the item validation code I need,
places and resizes the icons in the toolbar, provides all the behavior
when there's not enough room left (the overflow menu) etc.
Not being able to use the NSToolbar object for a toolbar would require
to reprogramm almost the whole toolbar object again.

Signature
Alexander
Michael Ash - 11 Oct 2007 20:49 GMT
> Not being able to use the NSToolbar object for a toolbar would require
> to reprogramm almost the whole toolbar object again.
Well, so much for that idea.
Back to your idea of using a normal window but positioned so that the
title bar is offscreen. You say that doesn't work because the title bar is
forced onto the screen. Have you tried subclassing NSWindow and overriding
constrainFrameRect:toScreen: to prevent the repositioning?

Signature
Michael Ash
Rogue Amoeba Software
Alexander Clauss - 11 Oct 2007 21:31 GMT
> Have you tried subclassing NSWindow and overriding
> constrainFrameRect:toScreen: to prevent the repositioning?
This is a good idea, and it works well. Thanks.

Signature
Alexander
Michael Ash - 12 Oct 2007 01:30 GMT
>> Have you tried subclassing NSWindow and overriding
>> constrainFrameRect:toScreen: to prevent the repositioning?
>
> This is a good idea, and it works well. Thanks.
Glad to hear it. One out of two isn't so bad. :)

Signature
Michael Ash
Rogue Amoeba Software