[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: NSMenu* and NSPopuUp* issues
From: |
Jeff Teunissen |
Subject: |
Re: NSMenu* and NSPopuUp* issues |
Date: |
Tue, 01 Apr 2003 05:46:06 -0500 |
Lars Sonchocky-Helldorf wrote:
> On 27.03.2003 11:22:10 "Philippe C.D. Robert" wrote:
[snip]
> >I'd say that since most Windows users tend to use their apps maximised
> >to fullscreen, there is no radical difference to the Mac menu bar - the
> >difference here though is that on Windows context sensitive menus are
> >much more common and much more used.
>
> Despite it looks nearly identical there is a HUGE difference: Those
> fullscreen Windows menus are still NOT AT THE EDGE of the screen. On the
> Mac I move the mouse with a short quick twitch of my wrist against that
> top edge and hit the menus while on Windows I have to move the mouse
> slowly so that I don't miss the menu.
Top-of-screen menus aren't much better. A twitch of your wrist does throw
the pointer in the correct direction, but that's _only_ useful for things
at the corners -- precision mousing is still needed to get to any other
menu. It helps with part of the problem, but not the whole thing, so if
the Windows app is maximized, a Mac's menus are not radically better.
NeXT-style menus are, in certain ways, better than either Windows-style or
Mac-style menus.
1. They take up less real space than either of the other two (less valid
against the Mac, but it is nonetheless true)
2. The space that they do use is on the sides of the screen, not the top
or bottom. Consider aspect ratios: 1.33:1 for TV-aspect, 1.78:1 for
widescreen. this means that vertical area is more "expensive" than
horizontal. This is also why the dock belongs on the side of the screen,
not the bottom -- though NeXT screwed that up, putting the dock 3 pixels
away from the screen's edge.
3. The operation of torn-off menus involves no secondary learning -- all
menus work alike, and the use of the close button reinforces that.
Torn-off menus in other environments (when they're allowed) look and act
awkward. This is a consistency problem that does not exist with NeXT-style
menus.
4. Mac- and Windows-style menus are only horizontal at the top level, then
they collapse into something very much like NeXT's...but without the title
bar to help out. Consistency problem.
> I speak here out of real life experience since I have to use Win 2k
> while on work but got a Mac at home.
Everyone else is speaking from real-life experience, too. You are not
unique in this regard.
--
| Jeff Teunissen -=- Pres., Dusk To Dawn Computing -=- deek @ d2dc.net
| GPG: 1024D/9840105A 7102 808A 7733 C2F3 097B 161B 9222 DAB8 9840 105A
| Core developer, The QuakeForge Project http://www.quakeforge.net/
| Specializing in Debian GNU/Linux http://www.d2dc.net/~deek/
- Re: NSMenu* and NSPopuUp* issues,
Jeff Teunissen <=
- Re: NSMenu* and NSPopuUp* issues, Philippe C.D. Robert, 2003/04/02
- Re: NSMenu* and NSPopuUp* issues, Fred Kiefer, 2003/04/07
- Re: NSMenu* and NSPopuUp* issues, Serg Stoyan, 2003/04/08
- Re: NSMenu* and NSPopuUp* issues, David Ayers, 2003/04/08
- Re: NSMenu* and NSPopuUp* issues, Richard Frith-Macdonald, 2003/04/08
- Re: NSMenu* and NSPopuUp* issues, Willem Rein Oudshoorn, 2003/04/08
- Contributing code issues (was: Re: NSMenu* and NSPopuUp* issues), Michael Hanni, 2003/04/08
- Re: NSMenu* and NSPopuUp* issues, Serg Stoyan, 2003/04/09
- Re: NSMenu* and NSPopuUp* issues, Richard Frith-Macdonald, 2003/04/09
- Re: NSMenu* and NSPopuUp* issues, Serg Stoyan, 2003/04/09