https://bugs.documentfoundation.org/show_bug.cgi?id=148648

            Bug ID: 148648
           Summary: Need to make Insert cross-ref more accessible
           Product: LibreOffice
           Version: Inherited From OOo
          Hardware: All
                OS: All
            Status: UNCONFIRMED
          Keywords: needsUXEval
          Severity: minor
          Priority: medium
         Component: Writer
          Assignee: [email protected]
          Reporter: [email protected]
            Blocks: 107905

Today, if I want to increase a cross-reference, I have to do one of the
following:

Option 1:

1. Remember the shortcut key for the Insert menu.
2. Press the shortcut key for the Insert menu.
3. Remember the shortcut key for Cross-Reference.
4. Press the shortcut key for Cross-Reference.
5. Remember that the shortcut needs to be pressed twice (Signature Line is
selected before Cross Reference for some reason).
6. Press the shortcut key for Cross-Reference again.
7. Press Enter.

Option 2:

1. Remember the shortcut key for the Insert menu.
2. Press the shortcut key for the Insert menu.
3. Take my eyes of the text.
4. Search the menu for Cross-Reference.
5. Press the shortcut key for Cross-Reference.
6. Notice nothing has happened, and realize another item was selected.
7. Press the shortcut key for Cross-Reference again.
8. Enter.

Option 3:

1. Take a hand off of the keyboard.
2. Click the Insert menu
3. Search for Cross-Reference
4. Click Cross-Reference


Options (1) and (2) are too cumbersome! And option 3 breaks my flow of working
with the keyboard.

I want to be able to make Insert | Cross-Reference more accessible.

Specifically:

1. There should be a global shortcut for Insert | Cross-Reference
2. The priority of Cross-Ref w.r.t. its shortcut key should be the first
selected upon pressing the shortcut.


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=107905
[Bug 107905] [META] Cross-references bugs and enhancements
-- 
You are receiving this mail because:
You are the assignee for the bug.

Reply via email to