Issue 68787 - The "Edit index entry" dialog can't follow the edited text
Summary: The "Edit index entry" dialog can't follow the edited text
Alias: None
Product: Writer
Classification: Application
Component: editing (show other issues)
Version: OOo 2.0.3
Hardware: All All
: P3 Trivial (vote)
Target Milestone: ---
Assignee: AOO issues mailing list
QA Contact:
Keywords: needmoreinfo
Depends on:
Reported: 2006-08-19 04:32 UTC by raindrops
Modified: 2013-08-07 14:44 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---


Note You need to log in before you can comment on or make changes to this issue.
Description raindrops 2006-08-19 04:32:04 UTC
I wanted to delete a certain Index Entry from my 336 page odt document. 
I used the "Edit index entry" dialog for this purpose.

Usually when the user clicks "next" button in the dialog, the cursor jumps to
the text where the index entry is inserted. That allows the user to check out
the text and then decide what to do with the index entry.

But often the cursor stops jumping to the next index entry.

When this happens, I see that Writer highlights one of the following:
(a)a cell of a table 
(b) An entire "nested table" (table that is inserted in another table)

After that, the index entry dialog shows the next entries, but the Writer stops
following the text. The screen keeps showing the highlighted part. As a result,
I can't see where the index entry is. The GUI does not even show the current
page number. It becomes very difficult to judge what to do. The only way out is
to close the dialog, skip some lines and start all over again.

A slightly older version of this defective file is with mru. (Private-Do not
post it here).
Comment 1 michael.ruess 2006-08-21 09:31:11 UTC
Reassigned to ES.
Comment 2 eric.savary 2006-08-21 14:54:38 UTC
Please, for this issue and further ones:
Anonymize your document (replace all chars with X) and attach a sample of the
whole document or only a part of it show the exact problem to EVERY issue you
write concerning "this" document.

Thank you!
Comment 3 raindrops 2006-08-21 15:48:42 UTC
Well, of course I HAVE attached several documents when necessary; but otherwise
this is one document I refer to. In last 8 months, I have reported 230
bugs/suggestions on the strength of that document (more than one issue per
working day); with an excellent acceptance ratio. 

So don't you think you should keep that document with you at all times? The idea
is to reduce work all around! :) 
Comment 4 eric.savary 2006-08-21 16:26:20 UTC
"Keep a document with you", "reduce work all around".
Exactly that.

It's not sure *I* or mru will care all the time of the issues (vacations, sick
leave... so on). So anyone who will be owner of the issue should have access to
the sample doc.
On the other hand, transmitting this to developpers causes extra mail traffic
pointing to the current version of your local document.
Consoder that always refering to an old, locally stored document causes a lot of
extra work.

Please consider we have a lot of other contributor and that we cannot have a
"personal tracking" of own documents especially over a long time.

So please be kind to always attach a sample document (try to reproduce from

Thank you.
Comment 5 eric.savary 2006-08-21 16:32:00 UTC
- insert the dummy text
- insert a table (about 10 rows) in the text
- in the table type many times the word "of"
- mark all "of" as index entries
- Start searching for the "of" entries in the entry dialog
-> when reaching the table, the cursor will jump back and forth avoiding the
table without reaching the entries in the table.

Same thin in OOo 1.1.5.
Comment 6 raindrops 2006-08-21 17:04:35 UTC
I do understand the problem.

It's only that I imagined that Sun/OOo provides a shared repository; and people
are able to share private documents confidentially by referring to it through a
URI. Apparently not. 

Besides, some of the problems seem related to the sheer size of the document(or
number of tables, etc). In the past, truncated documents have not produced the
same results. 

In this particular case, the problem occurred at so many places that I did not
have to pinpoint a location.

I will definitely create a fresh document whenever I can.
Thanks for your patience!
Comment 7 Oliver Specht 2006-08-22 08:03:35 UTC
Target changed to 2.x
->FME: Your job
Comment 8 Martin Hollmichel 2007-09-10 14:10:05 UTC
move to target 3.x according