Thoughts: Windows 8 should have eliminated the legacy right click menu.


Recommended Posts

Every regular forum visitor here knows how passionate I am about Windows 8, but there are a few things things that I would have done differently. I have been using Windows 8 on a regular basis across my devices, which includes both touch and non-touch hardware. I have come to the conclusion that Microsoft did not do enough to eliminate old, troubled paradigms from Windows to make them more "Modern", and one of those is the classic right-click menu. Now, there's a few reasons for this. It would make the right click menu more keyboard and touch friendly, while doing more to merge the old with the new.

Since Microsoft has the desktop enabled by default in all forms of Windows 8 and RT, there should have been more done to eliminate troubled code. The right click menu is just not satisfactory enough anymore, and since Windows 8 introduces the new "slide-out" menu on the right side of monitors, they could have easily added right-click menu functionality into the slide out menu. The Settings Charm would be the logical option to go with here. Now, obviously, I think the Charm would need to be re-named... "Functions", "Options", or something more consumer friendly along those lines.

Now, I know there are those that don't like Metro at all. Please, if you're just going to slam Metro and Windows 8, then obviously, now is the time to keep your thoughts to yourself. This is a discussion about a design option I feel should be there but isn't, and not one about whether or not Metro "sucks". Thank you.

Here's what it could look like on the desktop. The crossed off options are either better placed elsewhere, or are considered by me to be obsolete.

post-420821-0-59735300-1347042658_thumb.

The Explorer right click option is even more obsolete in Windows 8, due to much of the functionality appearing on the Ribbon at the top of the window. In fact, upon further inspection, ALL of the right click's functionality is duplicated in the Ribbon. So, it would be nice if the right click menu was gone, and I could access the entire Charms Bar (Win+C on the keyboard) just by right clicking here.

In essence, this guy's usefulness has come to an end, and should have been eliminated before Windows 8 RTM'd, but for some reason it was overlooked, and now users forced into the desktop on less than ideal devices have to put up with this, which is truly and awful experience. Microsoft, I hope you see this and take this into consideration for future releases.

Thanks.

Personally, I'm not a fan of the idea.. well I do like the concept, but not nuking the context menu entirely. Some of us have either customized and/or added on various shell extensions that really make that context menu rather large, never mind compatibility with previous stuff would be problematic or non-existant. Just between SVN and Git alone there's an awful lot of entries that would be problematic or cumbersome, and I've got a fair number more besides that from various utilities, scripts and whatnot.

Definitely make it in addition to what's already there, that would be handy in certain scenarios, but not kill it outright. I've dealt with context menus on a Windows tablet since the XP days, it's certainly not easy to hit accurately with a finger, and this setup would definitely be handy, but on a desktop system the context menu would just be a lot more convenient and efficient. Make it an optional and I'd be sold for sure.

  • Like 2

Thankfully they didn't do this. I like Windows 8, but the day they make a change like this is the day I switch to a different operating system.

On a touch screen, perhaps, but with a traditional keyboard/mouse set-up this would just be an annoyance and make people less productive (significantly more mouse movement).

You seem to completely miss one of the context menu's main advantages... :huh: (namely, the way they reduce the distance to your click target to zero or close enough)

I know this increases travel time, but with the way you can increase cursor speed today, it's a non issue. I can can cross my screens with only a slight bend in my wrist.

I know this increases travel time, but with the way you can increase cursor speed today, it's a non issue. I can can cross my screens with only a slight bend in my wrist.

So can I with a 5200 dpi RAT 5 mouse, the answer is the same.

So in what way is it an improvement then?

Use Windows on a tablet and try to bullseye the context menu items with your finger, it would be a huge improvement. Just needs to be an optional feature, on a desktop setup it would drive me batty having to navigate through a bunch of menus because of all the shell extensions I'm using, assuming they'd work at all. Simple on/off toggle and everybody's happy.

Ugh, no thank you. Usability has already taken enough of a hit as is.

There's no usability being lost here.

Personally, I'm not a fan of the idea.. well I do like the concept, but not nuking the context menu entirely. Some of us have either customized and/or added on various shell extensions that really make that context menu rather large, never mind compatibility with previous stuff would be problematic or non-existant. Just between SVN and Git alone there's an awful lot of entries that would be problematic or cumbersome, and I've got a fair number more besides that from various utilities, scripts and whatnot.

Definitely make it in addition to what's already there, that would be handy in certain scenarios, but not kill it outright. I've dealt with context menus on a Windows tablet since the XP days, it's certainly not easy to hit accurately with a finger, and this setup would definitely be handy, but on a desktop system the context menu would just be a lot more convenient and efficient. Make it an optional and I'd be sold for sure.

It could be something Microsoft could look into opening up for custom entries. It would certainly eliminate the amount of white space currently on the slide out.

I disagree completely! People know me as a big Windows 8 fan, but even I admit that there are certain UI paradigms that work better with mouse and others work better with touch. Context menus work great with mouse, but not touch. At the same time, buttons on the edge of the screen work better with touch. This is why using the Mail app in Windows 8 is so cumbersome. I have to travel my mouse in large distances using my mouse. Mail app using touch is fantastic. I propose that Windows 8 is more adaptable to mouse and touch. Both context menu and app bars should be present so all types of input can be used. Finally, I would suggest that the desktop context menu be the same as the Metro style context menu, just for the sake of consistency.

There's no usability being lost here.

There is indeed, everything about Windows 8 takes more clicks, more mousing around, more scrolling. Usability has taken a HUGE hit with Windows 8. This would be the icing on the cake.

It could be something Microsoft could look into opening up for custom entries. It would certainly eliminate the amount of white space currently on the slide out.

If it's an optional I'm all for it. In fact, if they'd extend the thing to not just simple menus but actual little "widgets" (whatever you'd want to call it), some little extensions that can do basic things besides a menu and it would be even more of a tasty option. Preview videos, view a changelog or edit a Subversion commit, toggle things on or off, etc etc.. lends itself to all sorts of possibilities. Put that RT stuff to good use.

There is indeed, everything about Windows 8 takes more clicks, more mousing around, more scrolling. Usability has taken a HUGE hit with Windows 8. This would be the icing on the cake.

I am just as productive on Win8 as I am on Win7, and the desktop is unchanged. So, define "everything" for me please...

  • Like 2

I am just as productive on Win8 as I am on Win7. Define "everything"....

No thank you, I'm not going to turn another thread into a why we don't like Windows 8, you said so yourself in your first post. My opinion is that this would be a big hit in terms of usability, which is likely the biggest reason I don't like Windows 8, so really, I'm surprised they didn't do this. Chalk it up to another feature that wouldn't be bad on a touch interface, but is terrible for a desktop. I like your creative thoughts, don't get me wrong, but I in no way think it's a good idea for a desktop. If you're offering it for a tablet, then perhaps it's not as bad of an idea.

No thank you, I'm not going to turn another thread into a why we don't like Windows 8, you said so yourself in your first post. My opinion is that this would be a big hit in terms of usability, which is likely the biggest reason I don't like Windows 8, so really, I'm surprised they didn't do this. Chalk it up to another feature that wouldn't be bad on a touch interface, but is terrible for a desktop. I like your creative thoughts, don't get me wrong, but I in no way think it's a good idea for a desktop. If you're offering it for a tablet, then perhaps it's not as bad of an idea.

Windows 8 is a new way to do old things, it's a fresh take on the desktop OS, but at the same time, it's incomplete. The little things like I detailed are why. If anything I certainly hope Microsoft updates their Mouse and Keyboard Center to support Windows 8 commands via my mouse. I'd settle for just invoking Win+I just by right clicking.

I am pretty sure 99% of the people would hate this option. There is a reason MS didn't do this: it would have been disastrous. I am going to say that context menus are not going away any time soon. Even in the next few versions of Windows.

  • Like 3

I am pretty sure 99% of the people would hate this option. There is a reason MS didn't do this: it would have been disastrous. I am going to say that context menus are not going away any time soon. Even in the next few versions of Windows.

It's not going away per se here either, just being moved to fill in the white space in the new slide out menu, while making things more universal. The current right click menu is a mouse driven bit that all users a re forced to deal with no matter what device they are using, which in Windows 8 makes no sense anymore when it can be moved to a better spot. It would still exist, as is, in third party apps, since Windows cannot possibly fill that role.

I know this increases travel time, but with the way you can increase cursor speed today, it's a non issue. I can can cross my screens with only a slight bend in my wrist.

Not so if you're on a laptop with a touchpad. Hence the app bars are a pain to use on a laptop. Depending on your sensitivity and speed settings, crossing the screen takes two finger swipes across the touchpad.

Sorry, still don't buy it. It would still be a terrible UI decision in my mind. People expect to get feed back at point of input, not some distance away. Context menu at the point of click is very natural for the brain and less jarring. I am going to say it now: as long as the mouse exists, context menus will continue to be at the point of click, not some distances away. But that's my opinion, but I know that's how it should be.

The Explorer right click option is even more obsolete in Windows 8, due to much of the functionality appearing on the Ribbon at the top of the window. In fact, upon further inspection, ALL of the right click's functionality is duplicated in the Ribbon. So, it would be nice if the right click menu was gone, and I could access the entire Charms Bar (Win+C on the keyboard) just by right clicking here.

Wouldn't that be an inconsistency, since right-click is used to activate the app bar and not the charms bar in Metro apps? It would be like a Start button that only appears on the desktop.

Not so if you're on a laptop with a touchpad. Hence the app bars are a pain to use on a laptop. Depending on your sensitivity and speed settings, crossing the screen takes two finger swipes across the touchpad.

Laptops are also getting special touch drivers pretty soon.

This topic is now closed to further replies.
  • Posts

    • BATorrent 3.0.2 by Razvan Serea BATorrent is a lightweight, open-source BitTorrent client built with modern C++ and Qt 6, offering a clean, fast, and privacy-focused alternative to traditional torrent apps. It supports magnet links, .torrent files, resume data, sequential downloading, per-file priorities, and even imports from qBittorrent. Power users benefit from integrated RSS auto-download with regex filtering, duplicate detection, and automatic tracker lists from Stremio. Streaming is seamless thanks to auto-detected players like VLC and IINA. BATorrent includes robust VPN tools—interface binding, auto-detection for WireGuard-based services like Mullvad and NordLynx, kill switch, proxy support, and IP filtering. A full WebUI enables remote control, while integrations with Plex, Jellyfin, and Emby automate library updates. With themes, speed scheduling, system-tray alerts, and cross-platform support for Windows, Linux, and macOS, BATorrent delivers a polished, high-performance torrenting experience. BATorrent features: Core .torrent file and magnet link support Resume data — picks up where you left off after restart Import torrents from qBittorrent Create .torrent files from any file or folder Sequential download mode Per-file priority control (skip, low, normal, high) Seed ratio limits with auto-pause DHT, PEX, UPnP, NAT-PMP RSS Auto-Download Subscribe to RSS feeds — automatically download new torrents as they appear Regex filters — match only what you want (e.g. 1080p|720p, S01E\d+) Per-feed settings — custom save path, check interval (5–1440 min), enable/disable Auto-download — matched items are downloaded automatically in the background Supports magnet links, .torrent URLs, and tags Tray notifications when items are auto-downloaded Duplicate detection — never downloads the same item twice Stremio Stremio Addon System pre-installed — works out of the box Auto tracker list from ngosang/trackerslist Streaming Play while downloading — stream video files before the download is complete Supports mp4, mkv, avi, mov, wmv, flv, webm, m4v, ts Auto-detects installed players (VLC, IINA, system default) VPN & Privacy Interface binding — lock torrent traffic to a specific network interface (e.g. tun0) Auto VPN detection — identifies VPN interfaces (tun, tap, WireGuard, Mullvad, NordLynx, ProtonVPN) Kill switch — automatically pauses all torrents if the VPN interface drops Auto-resume — resumes only the torrents paused by the kill switch when VPN reconnects Proxy support — SOCKS5 and HTTP proxy with optional authentication IP filtering — load P2P blocklists to block unwanted IP ranges Protocol encryption (enabled / forced / disabled) WebUI Remote management — control torrents from any browser at http://localhost:8080 REST API with JSON responses Add torrents via magnet link or .torrent upload Pause, resume, remove torrents remotely View peers and files per torrent Dark theme matching the desktop app HTTP Basic Auth with SHA-256 password hashing Configurable port and remote access (localhost vs 0.0.0.0) Interface 3 themes: Dark, Light, Midnight (bat/vampire aesthetic) Real-time speed graph Detailed panel with tabs: General, Peers, Files, Trackers Filter bar: search by name, filter by state (Active, Downloading, Seeding, Paused, Finished) Drag & drop .torrent files and magnet links Drag & drop reorder in torrent list System tray with notifications (download complete, kill switch events, RSS auto-downloads) Splash screen with bat animation Bilingual: English and Portuguese (BR), auto-detected from system locale Bandwidth Scheduler Alternative speed limits — set different download/upload limits on a schedule Time range — configure active hours (e.g. 01:00 to 07:00), supports overnight ranges Per-day control — choose which days of the week the schedule applies Automatically switches between normal and alternative speeds Media Server Integration Plex — automatically trigger library scan when a download completes Jellyfin / Emby — same automatic library refresh via API Configure server URL and authentication token/key in Settings System Cross-platform: Windows, Linux, macOS Auto-shutdown — automatically shut down PC when all downloads complete (60s cancellable countdown) Auto-update system (AppImage on Linux, installer on Windows, DMG on macOS) CLI arguments: pass .torrent files or magnet: URIs directly Keyboard shortcuts: Space to toggle pause, Ctrl+A to select all, Ctrl+O to open BATorrent 3.0.2 changelog: Phone pairing & WebUI The browser WebUI was reskinned to match the desktop app — same dark palette, Inter font, flat surfaces, the real BATorrent logo (it was a random bat before), and a proper magnet icon. It now looks like the same product, not a separate dashboard. Pairing is one tap and zero typing: the generated WebUI password is now copyable, and the QR code carries the credentials — scanning it from your phone logs straight in (no typing the IP or password), then drops the credentials from the address bar. Search Two new providers: RuTor (CIS sources, no login, via a public TorAPI relay) and Torrents-CSV. Results are sorted by seeders (healthiest first), and each search now times out after 15 s so one dead provider can't hang the UI. Files & trackers Per-file priority is back: right-click a file in the detail panel to set Skip / Low / Normal / High. Rename an individual file inside a torrent (double-click or the file menu), separate from renaming the torrent. Remove a tracker from a torrent (the ✕ on a tracker row); adding was already there. Smart Paste on Ctrl+V — paste a magnet, a 40-char info-hash, or a .torrent URL straight from the clipboard and it's added immediately (text fields still paste text normally). Covers & titles Anime fansub naming ([Group] Title - NN) now resolves to the right show. Audio channel layouts in titles (DDP5.1, 7.1, …) are stripped so they don't pollute cover matching. Under the hood The legacy QWidget interface is gone. QML had been the only UI since 3.0.0 (reachable old code lived behind a hidden --legacy flag); with parity confirmed, the entire QWidget layer — main window, every dialog, the theme manager — was removed (~13,400 lines). The four restored actions above were features that backend already supported but the QML port had never wired. macOS: the WebUI password hash moved out of the keychain into app settings, so launching the app no longer pops a login-keychain password prompt on unsigned builds. The actual password still lives in the keychain. Cleanup: ~400 orphaned translation strings and a batch of dead code removed; internal duplication collapsed; an ARCHITECTURE.md added for contributors. Unit / security / memory tests and the ASan/UBSan/TSan sanitizers stay green. Download: BATorrent 3.0.2 | 30.5 MB (Open Source) Download: BATorrent Portable | 42.3 MB Links: BATorrent Website | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • How about a global switch to turn the awful things off instead of a registry hack? Then everyone wins.
    • This doesn't strike me as so shocking when... " IT admins do have some control over this rollout. If they choose to opt out, devices in their tenant won't automatically get the dreaded Copilot app"
  • Recent Achievements

    • Mentor
      grik went up a rank
      Mentor
    • Dedicated
      JKR earned a badge
      Dedicated
    • One Year In
      CHUNWEI earned a badge
      One Year In
    • Conversation Starter
      FBSPL earned a badge
      Conversation Starter
    • Week One Done
      I2D earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      468
    2. 2
      PsYcHoKiLLa
      257
    3. 3
      Skyfrog
      79
    4. 4
      ATLien_0
      60
    5. 5
      FloatingFatMan
      60
  • Tell a friend

    Love Neowin? Tell a friend!