Linked by Thom Holwerda on Wed 6th Jun 2012 19:24 UTC
Windows One tiny thing I wanted to mention about Windows 8: ever noticed how context menus in Metro appear above the mouse cursor instead of underneath? I'm assuming this is done because of finger input (by opening above, your finger and hand doesn't cover the menu), but with a mouse, it's just plain weird. Fun little detail though - shows you how much thought has gone into the touch aspect of Windows 8.
Thread beginning with comment 521059
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[3]: ...
by cfgr on Wed 6th Jun 2012 21:24 UTC in reply to "RE[2]: ..."
cfgr
Member since:
2009-07-18

There is no reason to break conventions just for the sake of breaking them. That's just stupid. It makes sense to have the popup menu above the touch event, but not for a mouse click if that's the normal behaviour.

I understand the idea behind Metro, I just think it's very poorly executed. They want to build a system that can turn laptops into tablets but they seem to forget that once you arrive at your desk, you want to use that laptop as a workstation. Metro makes the latter harder.

I wouldn't mind as much if Microsoft showed clear intentions to optimise the conventional desktop so actual work can be done conveniently on the same device. However, every signal from them seems to point in the wrong direction. It's all about picking the right tool for the job, Metro is not the right tool for actual work. And that's OK, as long as it's possible to pick another tool for the job.

KDE is going the right way. Even Linux and the Unixes are going the right way as you can perfectly install multiple desktops and nothing stops you from switching between them for tablet/workstation use.

Edited 2012-06-06 21:30 UTC

Reply Parent Score: 4

RE[4]: ...
by Nelson on Wed 6th Jun 2012 21:30 in reply to "RE[3]: ..."
Nelson Member since:
2005-11-29

There is no reason to break conventions just for the sake of breaking them. That's just stupid. It makes sense to have the popup menu above the touch event, but not for a mouse click if that's the normal behaviour.


Let me make a few things clear:

- This is only for Metro Styled context menus. Win32 rendered ones are the same
- Metro Style guidelines dictate that most frequently used items are near the bottom (opposite of Win32)
- Metro Style guidelines dictate that a Context Menu contain no more than six (6) menu items.

Since this is true, your mouse travels the same distance it otherwise would have with a Win32 context menus.

Reply Parent Score: 2

RE[5]: ...
by cfgr on Wed 6th Jun 2012 21:34 in reply to "RE[4]: ..."
cfgr Member since:
2009-07-18

- This is only for Metro Styled context menus. Win32 rendered ones are the same

You completely miss my point that Microsoft is pushing towards Metro everywhere.

- Metro Style guidelines dictate that most frequently used items are near the bottom (opposite of Win32)

That's the thing. It dictates stuff that's stupid from a workstation point of view. If they did it the smart way, they would just show the menu upside down above the event in "touchscreen mode", and show it normally in "classic mode". But support both modes.

- Metro Style guidelines dictate that a Context Menu contain no more than six (6) menu items.

Same thing. It's about Metro dictating things that are good for tablet use and utterly stupid for workstation use.

Reply Parent Score: 1