Bug 75103 - CONFIGURATION: Change right click menu order to most used to least used
Summary: CONFIGURATION: Change right click menu order to most used to least used
Status: RESOLVED DUPLICATE of bug 71770
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: UI (show other bugs)
Version:
(earliest affected)
4.2.0.4 release
Hardware: Other All
: medium enhancement
Assignee: Not Assigned
URL:
Whiteboard: BSA
Keywords:
Depends on:
Blocks:
 
Reported: 2014-02-17 16:12 UTC by Zeki Bildirici
Modified: 2014-09-20 13:56 UTC (History)
0 users

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Zeki Bildirici 2014-02-17 16:12:50 UTC
Problem description: 

Cut, Copy and Paste functions are most used actions n right click context menu. However they are placed the bottom of the menu, which makes user tired and lose time(You may not use the keyboard everytime, you may be holding a report or checking another list from paper by pen) even most users don't know the shortcuts, or anyway, its everydays cut&copy&paste.

I my 17" computer screen with 1024x768 resolution ieed to move the cursor nearly 1/2 and 1/3 of the screen to reach cut, copy and paste functions.


Screen has 21 cm height and i move my cursor about
Writer ~11 cm
Calc   ~6 cm
Impress ~10 cm

to reach this action items after a right click.

I dont know if there is a proper reason for this order but, for me this menu order is not helping. A regular user doesn't click to page settings more than cut&copy and paste, or clicks to comments, or line spacing.

It's obvious that Cut, Copy and Paste is most clicked actions. Thus please change the order for a logical hierarchy to stop this torture.

Current behavior:

Cut&Copy&Paste action items are placed at the bottom of the menu context.

Expected behavior:
Move them top to reach easily and save time.

Best regards,
Zeki

              
Operating System: All
Version: 4.2.0.4 release
Comment 1 A (Andy) 2014-09-20 13:56:20 UTC

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