2 ms·
"The best that we can say is that both approaches provide advantages." The best we can say is that Fitts's Law says that the one menu bar approach is better, a
by jimbokun 18y ago
"The best that we can say is that both approaches provide advantages."
The best we can say is that Fitts's Law says that the one menu bar approach is better, and I do not know of any UI research or design principles at all favoring the one-menu-bar-per-window approach.
http://www.asktog.com/basics/firstPrinciples.html#fittsLaw http://www.asktog.com/basics/firstPrinciples.html#fittsLaw
"Fitts' law (properly, but rarely, spelled "Fitts's Law") dictates the Macintosh pull-down menu acquisition should be approximately five times faster than Windows menu acquisition, and this is proven out."
- pdubroy 18y agoIt's an oversimplification to say the the four corners of the screen are the fastest targets to point at. According to Fitts' Law, the time to point to a target is a function of the distance to the target and the size of the target. In some cases that may be the corners of the screen (because they effectively have an infinite target size). But if the corners are very far away (as can be the case on large screens), then other nearby targets can be faster to acquire. So, on a small screen, the Mac approach might be faster. On a large screen where the window size is a smaller fraction of the display size, the Windows approach might be faster. But Fitts' law doesn't tell the whole story -- there's more to consider than just the raw target acquisition speed. What about the time you spend figuring out where the target is? That's probably lower with a single menu bar, because it's always in the same place no matter where the window is. But if the application has lots of controls in the toolbar, you might find that people instinctively start moving towards the toolbar first, before realizing that the command they need is actually in the menu bar. On Windows, it's a slight correction to start heading for the menu bar; on OS X, it might be a completely new movement. A better example of how the multiple menu bar approach might be better: on a large monitor, when I have several non-overlapping windows, I sometimes head to the menu bar, only to realize that the wrong application is active. So I have to move the mouse again, select the correct window, then go back to the menu bar to make my selection. With multiple menu bars, this problem doesn't occur.
- ars 18y agoYou're forgetting that first you have to make the right application active. And the only way to tell which application is active is the slight brightness. And even worse the applications have no titles, so you have to be able to recognize the application you want by the shape of the window instead of it's name. And that's why I don't like the unified bar. With multiple bars you can directly click on the action you want, even if the app is not active. And it's easy to tell what application it is because it's titled. Plus it's impossible to use focus on mouse (i.e. move the mouse over an app and it's active, but doesn't move to the front) with a single bar. And I find focus on mouse increases productivity quite a bit. And even fitts law isn't right, because the mouse will often be in the window you are working on, but to get to the bar you have to move all the way to the top, do it, then come back to where you were. With separate bars the distance is quite less.