Do you (still?) find bringing up Charms with mouse to be clumsy/difficult?

By contextfree
in The Fast Ring (Insider Previews)

 Share

Recommended Posts

Experienced

Wyn6

Posted
Posted

Charms and/or the Switcher work nice and fluid for me. I use a "swooping/swinging" motion as well. There's no impediment to the user, perceived or otherwise. Although, some may argue the "perception is reality" adage. Once you become accustomed to it, it's like second nature.

The majority of my time since RP is spent on the Metro side. Now, let me qualify this by saying, I work with a number of desktop app, but I launch all of them from the Start Screen. I use the Metro web browser a ton more than the desktop browser. Switching tabs is certainly faster in the desktop, but again once you acclimate, it's pretty fast in IE Metro too. Since, all my news readers, Tweetro, and things I use all day are on the Metro side, using IE Metro keeps me in one environment the entire time.

Although, I must say that going from desktop to Start Screen isn't really an issue. Especially, considering I'm in snapped mode 90% of the time. I wish individual desktop apps would appear in the Switcher. Ah well. Overall, I find 8 a pleasure to use and like it much better than 7, and certainly its potential.

Mentor

grayscale

Posted
Posted

I'm used to opening up the start menu or whatever by just winkey+start-typing so charms bar is not that much of a hassle since it's just winkey+c (although I don't think corners are too much of a hassle since you don't need to 'target' it. You only need to go all the way to the corner and down.

Grand Master

theyarecomingforyou

Posted
Posted

I find myself trying to trigger it on Windows 7. Needless to say, it's becoming second nature.

Same, but that doesn't mean it's not clumsy. On multi-monitor systems you have to make sure you hit the catchment area, then when moving the mouse to trigger it you have to be careful to move vertically or else it will disappear - there is reasonable margin but it becomes more of an issue when you're trying to do it quickly. The biggest problem is that you can lose track of the cursor on the second monitor, which is especially problematic if the display isn't immediately next to the first (I have a HDTV connected at a 90 degree angle for watching media). I've adapted to it as best I can but it's still not a good UI element.

Experienced

Wyn6

Posted
Posted

Same, but that doesn't mean it's not clumsy. On multi-monitor systems you have to make sure you hit the catchment area, then when moving the mouse to trigger it you have to be careful to move vertically or else it will disappear - there is reasonable margin but it becomes more of an issue when you're trying to do it quickly. The biggest problem is that you can lose track of the cursor on the second monitor, which is especially problematic if the display isn't immediately next to the first (I have a HDTV connected at a 90 degree angle for watching media). I've adapted to it as best I can but it's still not a good UI element.

I only have one monitor running at the moment 42" HDTV. Are you running the RP? Thought it was supposed to have better multi-monitor support.

Grand Master

Dot Matrix

Posted
Posted

I only have one monitor running at the moment 42" HDTV. Are you running the RP? Thought it was supposed to have better multi-monitor support.

It does. The multi monitor support in the RP is phenomenal, but it is a bit quirky yet. It's getting there.

Grand Master

theyarecomingforyou

Posted
Posted

I only have one monitor running at the moment 42" HDTV. Are you running the RP? Thought it was supposed to have better multi-monitor support.

I'm running the RP but to be honest it created as many problems as it solved. For instance, dragging a Metro apps off the edge of a screen automatically maximises it to the next screen; the new corner catches don't recognise Aero Snap; opening the Start screen moves onto that monitor any Metro apps running on another monitor (meaning if you have two screens you can't run Metro apps on both screens). The changes were poorly thought through.

This topic is now closed to further replies.
 Share
Go to topic listing

  • Recently Browsing   0 members

    • No registered users viewing this page.

  • Posts

    • Meta is reusing old DDR4 RAM in its servers instead of buying new hardware

      By sava700 · Posted

      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 Copernic · Posted

      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 Copernic · Posted

      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
    • Dbrand thought they could get away with this Steam Machine case, Valve disagreed

      By Doli · Posted

      "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.
    • Can't access the forum on mobile

      By WITHOUT-ME · Posted

      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
    Show More

  • Tell a friend

    Love Neowin? Tell a friend!