Bug 137704 - Enable Edit > Index when cursor is not on a field
Summary: Enable Edit > Index when cursor is not on a field
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
7.0.2.2 release
Hardware: All All
: medium enhancement
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: Fields-Dialog
  Show dependency treegraph
 
Reported: 2020-10-23 12:06 UTC by RichardKirk
Modified: 2023-03-02 01:02 UTC (History)
3 users (show)

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 RichardKirk 2020-10-23 12:06:41 UTC
Description:
I am using 7.0 and I have just got to grips with making an index I think. I appreciate this is is work in progress, but I feel a small change might make a lot of difference. At the moment you have to make the index entries visible by enabling Field Shadings, then select an entry, the right click on it to see the edit dialogue.

Suppose the edit dialogue could be bought up from wherever the cursor currently is by right-clicking. If you were not on a current index there would be no current index entry, but you could still go to the next or the previous index using the buttons (so making them visible is not as important - make them visible when the dialogue is up). You could also create an index entry from this menu, just like the other dialogue. You would not have to close this dialogue to create a new entry - just move the cursor.


Steps to Reproduce:
N/A

Actual Results:
N/A

Expected Results:
N/A


Reproducible: Always


User Profile Reset: No



Additional Info:
N/A
Comment 1 Heiko Tietze 2020-11-12 08:49:57 UTC
The command could remain disabled when the whole document does not contain any field. But otherwise the dialog shows up with empty Type, Select, Format lists but the next/prev buttons are available.
It wouldn't find any previous field if the cursor is at the beginning of the document (and similarly for the end and next), so ideally we can disable the buttons depending on the position.

An alternative solution could be to introduce fields at the Navigator.
Comment 2 Dieter 2020-11-12 10:54:36 UTC
(In reply to Heiko Tietze from comment #1)
> An alternative solution could be to introduce fields at the Navigator.

I think this is bug 137741
Comment 3 sdc.blanco 2023-03-02 01:02:21 UTC
Halfway solution:
Use Tools - Customize to add "Go to Next Index Mark" and "Go to Previous Index Mark" (search on "Index" in the Customize Dialog) to {toolbar, context menu, shortcut key}, according to preference. This will move the cursor from an arbitrary position to an index entry, but you still need to open Index Entry.  

(Could make a custom toolbar with these two commands, plus .uno:IndexEntryDialog, which opens the Edit Entry dialog, when the cursor is on an Index Entry (there are two "Insert Entry" options).  You still have to close the Edit dialog each time, but it might make life a little easier.