Bug 109656 - Usability: RMB menus and Menubar menus should be in similar order and grouping
Summary: Usability: RMB menus and Menubar menus should be in similar order and grouping
Status: RESOLVED DUPLICATE of bug 92905
Alias: None
Product: kmail
Classification: Applications
Component: keys and menus (show other bugs)
Version: unspecified
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-07-26 17:33 UTC by Erik Hensema
Modified: 2009-12-21 20:34 UTC (History)
4 users (show)

See Also:
Latest Commit:
Version Fixed In:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Erik Hensema 2005-07-26 17:33:57 UTC 
Version:            (using KDE KDE 3.4.1)

When right-clicking on a mail folder, you are presented some options. These options are also accessible from the Folder menu in the kmail menu bar.

However, the Folder menu also contains additional entries. The layout differs too.

I think both menus should be similar in both looks and entries. This would enhance usability.
Comment 1 Celeste Lyn Paul 2005-10-05 04:01:52 UTC 
The RMB menu and the Menubar menu options should be in same order.  Items should also be grouped together in the same way, with a bar separating each group of menu items.

Eg: "Mark All Messages as Read" and "New [Sub]folder" should be in the same order in both the RMB menu and the Menubar:Folder menu.

Eg: "Expire..." should be grouped with the rest of the Menubar:"Folder" items because folder expiration is found in this group.
Comment 2 Luis Silva 2008-11-25 11:30:23 UTC 
Kmail in kde 4.1.3 still presents this bug but the menus radically differ now.
As a user I would expect them to. I use the RMB menu for basic operations as deleting or marking all mesages as read ad the "real" menu for all the res.
Comment 3 Jonathan Marten 2008-11-25 18:10:21 UTC 
See also bug 92905.
Comment 4 Björn Ruberg 2009-12-21 20:34:14 UTC 

*** This bug has been marked as a duplicate of bug 92905 ***