Bug 69342

Summary: A way to identify which actions are carried out on different mouse clicks on context menus
Product: [I don't know] kde Reporter: Paul Sprakes <pauls>
Component: generalAssignee: Unassigned bugs mailing-list <unassigned-bugs>
Status: RESOLVED INTENTIONAL    
Severity: wishlist CC: nate
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: Compiled Sources   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Paul Sprakes 2003-11-30 12:58:34 UTC 
Version:            (using KDE Devel)
Installed from:    Compiled sources

When you right click on an item in kde you get a context menu which lists all actions you can carry out on that item. I think it would make sense to visibly identify which actions are carried out if the user where to left click or middle click on that item.

This is similar to showing the keyboard shortcuts against menu entries and helps the user find quicker ways of doing things as they use the application.

Example:

The user right clicks an html file in konq file manager. On the context menu these items would appear:

Open with konqueror   LMB
Open with kwrite      MMB
Cut                   CTRL+X
Copy                  CTRL+C
etc....

I would also suggest that the LMB and MMB actions are the first two entries that appear on every context menu.
Comment 1 Waldo Bastian 2005-03-24 19:35:59 UTC 
Too much visual clutterand "MMB" and "LMB" are very cryptic.
Comment 2 Dotan Cohen 2008-01-05 12:46:57 UTC 
This bug was closed as WONTFIX because the suggestion that "LMB" and "MMB" are cryptic. I propose that instead of "LMB", the context menu have the LMB action as the first action, in bold text. I have no good suggestion as for what to do about "MMB". Maybe it should be the second menu item, in an italic text?

This would remove the guesswork about what will happen when clicking on certain files. For instance, do HTML files open in Firefox or Kate (web devs open local HTML files for editing).
Comment 3 Nate Graham 2020-09-30 04:39:51 UTC 
Not sure we'll be able to implement this, sorry. :)