Metro/Modern UI & shorter mouseways


Recommended Posts

Microsoft explained that the Mouseways (is this the correct english word? :$ ) should be shorter in the new startscreen than in the startmenu.

I don't get it.

4qrdo.gif?1

Can samebody explain me the new shorter mouseways again? This should not be a pro/contra startmenu discussion.

But the argument from Microsoft is just... wrong. You could say a cheek.

Link to comment
https://www.neowin.net/forum/topic/1115237-metromodern-ui-shorter-mouseways/
Share on other sites

but is makes it less clear. Maybe not in my case because I just have a few icons there.

Larger targets make things easier to see, and click with the mouse, while not having to be as precise.

I have problems to find easier the big icons than the small. Because at the small icons I can read more rows to the same time. At the big I can just focus one and have to search.

Apart from larger hit area vs. actual mouse travel, I think one more reason is them wanting an interface both for touch and mouse|keyboard as well (I'm not saying 'designed exclusively for touch'). Whether reading or just 'seeing' the icons is better for the user, at least by the Start Screen, it will be usable to both touch and keyboardmouse users. Now whether users will get used to a full screen menu, it's almost split, the way I see it (based on reactions here on the forum). I personally don't mind the new one since I'm more used to launching my programs using the keyboard.

I have problems to find easier the big icons than the small. Because at the small icons I can read more rows to the same time. At the big I can just focus one and have to search.

With the Start Screen it's designed to be highly customisable, so most users will group together apps as they wish (as the screenshot in fact shows) - it makes it much quicker to locate them once you're used to it. As with everything, it does take a while to adapt to the new system and it will seem more awkward at first, just as the Office ribbon UI did. The advantage of the Start Screen if you have have 80-90 apps on screen at a time, which simply wasn't possible/practical with the Start Menu. If you're only using a handful of apps - like the Start Menu in the picture - you're better off pinning them to your taskbar or adding shortcuts to the desktop.

That said, I wish the icons for non-Metro apps were larger. Sure they're much larger than the initial Developer Preview but there's still a lot of wasted space and the icons are one of the most easily identifiable features when locating a program. It would also be nice if there were addition options, like being able to colour code the backgrounds of groups and leaving gaps.

but is makes it less clear. Maybe not in my case because I just have a few icons there.

I have problems to find easier the big icons than the small. Because at the small icons I can read more rows to the same time. At the big I can just focus one and have to search.

Once you've customized your start screen, you should be able to mentally adjust (in a day or so):

- do I have to click my mousewheel down once or twice to put the item into view?

- how much force should I put into the mouse to make it land on the tile of the program I want to start?

That is, you can make the Start Screen work off muscle memory.

This is arguably much faster than the old start menu, which requires you go to All Programs, then scan through a list (or open a program group), then target, EVERY TIME.

One tweak you can do is for the Close gesture using the "Close Threshold for Metro Apps" tool from Winaero: http://winaero.com/comment.php?comment.news.101 Then you don't have to drag the mouse pointer all the way to the bottom to close an app, if you adjust it to somewhere along the middle of the screen.

There is of course Alt+F4.

Once you've customized your start screen, you should be able to mentally adjust (in a day or so):

- do I have to click my mousewheel down once or twice to put the item into view?

- how much force should I put into the mouse to make it land on the tile of the program I want to start?

That is, you can make the Start Screen work off muscle memory.

This is arguably much faster than the old start menu, which requires you go to All Programs, then scan through a list (or open a program group), then target, EVERY TIME.

The most used apps I pined to the front so I actually never use the "all programs" and scroll.

Fitts law is not just about "distance."

http://en.wikipedia....i/Fitts%27s_law

Quite, Fitt's law is more about speed / ease - and things being small and close together can negatively effect that.

To the OP: the argument is is that it's quicker / easier to hit more larger hit targets on the start screen with a lower error rate (even if they're further away), then it is to hit specific smaller, closer together targets on the start menu. They had a picture on one of the building Windows 8 blogs that colour coded how the calculations worked out wih respect to how easy / quick accurate it is to get to a specific buttons.

The most used apps I pined to the front so I actually never use the "all programs" and scroll.

Still applicable. Simply pin the larger format icons to the left side of the Start Screen.

Remember, the action in the old start menu is targeting. With the new start screen you just have to remember to "throw" your mouse in the general vicinity and click. Because the targets are larger, you can afford to move your cursor faster to make up for the distance.

Here's a small test:

Install 50+ applications in W7 and W8.

Try to find random apps in W7 start menu and CLICK it.

Do the same in W8.

Assuming W8 start screen is organized, you will ALWAYS be able to find and click it faster than W7.

Still applicable. Simply pin the larger format icons to the left side of the Start Screen.

Remember, the action in the old start menu is targeting. With the new start screen you just have to remember to "throw" your mouse in the general vicinity and click. Because the targets are larger, you can afford to move your cursor faster to make up for the distance.

I'm a lot faster to use the list from the menu instead of the screen. I have to move the mouse about the entire screen, I waste a lot of time (time is relative ^^)with it, In this time I would have the program started with the list in the menu.

I'm a lot faster to use the list from the menu instead of the screen. I have to move the mouse about the entire screen, I waste a lot of time (time is relative ^^)with it, In this time I would have the program started with the list in the menu.

No, you can not except some pinned apps in start menu. There is taskbar for that.

This topic is now closed to further replies.
  • Posts

    • The fact that memory in general is so high I have to take a loan out to build a computer now is just beyond stupid. Who's really to blame here? Low supply or high demand?
    • Display Driver Uninstaller (DDU) 18.1.5.5 by Razvan Serea Display Driver Uninstaller (DDU) is a utility for completely removing AMD/NVIDIA/INTEL graphics drivers and related packages from your system, attempting to eliminate all leftovers (including registry entries, folders and files, driver store). Though AMD/NVIDIA/INTEL drivers can usually be removed via the Windows Control Panel, this uninstaller tool was created for situations where standard uninstall fails, or when you need to fully remove NVIDIA or ATI graphics card drivers. After using this driver cleaner, your system will behave as though it’s the first time you’re installing a new driver—similar to a fresh Windows installation. As with all such tools, we recommend creating a restore point beforehand, allowing you to undo changes if issues arise. If you're having trouble installing an older or newer driver, try it—there are reports that it resolves such problems. Recommended usage: The tool can be used in Normal mode but for absolute stability when using DDU, Safemode is always the best. Make a backup or a system restore (but it should normally be pretty safe). It is best to exclude the DDU folder completely from any security software to avoid issues. You do NOT need to uninstall the driver prior using DDU. Requirements: .NET Framework 4.8 Compatible with Windows 7, 8, 8.1, 10, and 11 (32-bit or 64-bit) Note: Using on Insider Preview builds is at your own risk. Display Driver Uninstaller (DDU) 18.1.5.5 changelog: Added 'Reset to recommended' button for the Options. General fixes and improvements. Download: Display Driver Uninstaller (DDU) 18.1.5.5 | 1.7 MB (Freeware) Download: DDU Portable | 1.2 MB Links: Display Driver Uninstaller Home Page | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • WACUP 1.99.51.24568 Preview by Razvan Serea WACUP (WinAmp Community Update Project) is a modern, enhanced version of the classic Winamp music player, designed for better stability, performance, and compatibility. Built for Windows, WACUP retains the familiar Winamp interface while adding 64-bit support, bug fixes, and new features like improved audio format support, customizable skins, and optimized playlist management. Unlike bloated alternatives, WACUP focuses on lightweight performance and regular updates, making it the best choice for fans of the classic Winamp experience. Basically, if you miss the good old days of Winamp and want a modern upgrade that doesn’t mess things up, WACUP is for you! WACUP key features: Classic Winamp Feel – Keeps the familiar interface and functionality. Bug Fixes & Stability – Fixes old Winamp issues and improves performance. 64-Bit Support – Works better on modern systems. More Formats & Plugins – Supports additional audio formats and third-party plugins. Customizable UI – Skins and tweaks for a personalized look. Better Library Management – Improved playlists, media organization, and search. No Bloat – Focuses on performance without unnecessary extras. Regular Updates – Community-driven development with new features and fixes. WACUP 1.99.51.24568 Preview changelog: Fixed a deadlock seen from the recent crash reports when doing some of the drag + drop actions within the media library window Fixed a loading crash seen related to a problem with some of the artwork cache image files being restored which should now be better handled allowing for the bad image to be removed without it failing Fixed a deadlock seen from the recent crash reports when the internal metadata cache clearing is triggered which could block the main ui thread for too long with this now being moved to a background thread Fixed some performance issues with some of the methods related to determining artwork support which mainly affected the local library import / refresh (this is still slower for some compared to other players because there's more data & artwork aspects being checked for which means doing more processing on a single file despite the best of attempts to reduce duplicate / heavy processing where possible) Fixed a crash with the JTFE based missing files hotkey which no one seems to have used for an age for this to appear (maybe it's time to seriously consider stripping out features that aren't being used) Fixed how some of the file types which use extra information to reference their sub-songs is handled which was preventing some from being correctly resolved back to their base file (noticed fixing above) Fixed an issue with the handling of files with underscores in their filepath which wasn't being correctly handled causing some of the filename to be lost when shown as the title if title reading is delayed Fixed a few things that might be behind NotSoDirect not being stable for some setups though am still not certain that the changes done for this are going to fully resolve the problem from the crash reports Fixed the OS toast handling when there's no prior shortcut in the OS start menu to now create the shortcut (needed to allow the yes/no buttons for the new build / post-release toast) to be done as a hidden one so it's less likely to cause annoyance for those not wanting to see it whilst still allowing this less than ideal OS api implementation requirement to be met to avoid toasts without the needed buttons Fixed a regression when moving from taglib1 to taglib2 which broke some of the handling in place to allow for external programs to still access files when wacup has a held open cached instance of the file Everything else Updated cppwinrt (gen_win10shell.dll) to 3.0.260520.1 (26 May 2026) Updated libcurl (libcurl.dll) to 8.2.1 (24 Jun 2026) Updated Monkey's Audio (in_ape.dll) to 13.15 (28 Jun 2026) Updated mpg123 (mpg123.dll) to 1.33.6 (6 Jun 2026) Updated OpenSSL (libcurl.dll) to 3.5.7 (9 Jun 2026) Updated pugixml to 1.16 (16 Jun 2026) Updated taglib (tag2.dll) to 2.3.0 (11 May 2026) Updated vgmstream (in_vgmstream.dll) to the latest Git commit from 28 Jun 2026 Download: WACUP 64-bit | 9.6 MB (Freeware) Download: WACUP 32-bit View: WACUP Website | Screenshots Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • "over a thousand engineering hours" and started selling it but could not take a couple of minuets to send an AI email to ask permission. What an expensive lesson.
    • just tested it yesterday, a simple page with autoloading ADS takes 60mb....just 1 page for 60 megabytes.   poor people with a limited internet never will visit neolose
  • Recent Achievements

    • Week One Done
      Collagen Project earned a badge
      Week One Done
    • Reacting Well
      Wakeen1966 earned a badge
      Reacting Well
    • Rookie
      Almohandis went up a rank
      Rookie
    • Apprentice
      jahara21 went up a rank
      Apprentice
    • Reacting Well
      NovaEdgeX earned a badge
      Reacting Well
  • Popular Contributors

    1. 1
      +primortal
      526
    2. 2
      +Edouard
      265
    3. 3
      PsYcHoKiLLa
      146
    4. 4
      Steven P.
      99
    5. 5
      macoman
      55
  • Tell a friend

    Love Neowin? Tell a friend!