Apache OpenOffice (AOO) Bugzilla – Full Text Issue Listing
|Summary:||Refreshing an index jumps|
|Component:||ui||Assignee:||AOO issues mailing list <issues>|
|Status:||ACCEPTED ---||QA Contact:|
|Priority:||P3||CC:||issues, max.odendahl, thomas.lendo|
|Issue Type:||ENHANCEMENT||Latest Confirmation in:||---|
Description moritzmhq 2002-08-02 13:20:01 UTC
If you have a large index/ToC and update it, the view always jumps to the start of the index. This is annoying as hell and makes fixing an index much harder than it ought to be. FIX: Keep view position after Refreshing an index with RMB->"Verzeichnis aktualisieren".
Comment 1 Unknown 2002-11-02 11:40:05 UTC
bug persists with build 643. Could we change priority to a higher level??
Comment 2 eric.savary 2003-01-31 16:00:18 UTC
Higher level means -> crash. So it can't have this prio. ES->OS: I think it's not so easy to "fix"...??? Does it need to go through the PM Team first?
Comment 3 Unknown 2003-01-31 17:38:43 UTC
ES wrote: >> Higher level means -> crash. So it can't have this prio. Ok, will try to stick to the exact terminology in the future.. This bug really is - as Morhippo described it before - "annoying as hell" and therefore unfortunately disqualifies this Linux-Build of OO for any sort of larger structured documents IMHO. It even caused me to switch to the Windows Build when working on an academic document which was indexing not more than 30 entries in the ToC...
Comment 4 Oliver Specht 2003-02-03 08:42:13 UTC
->Christoph: I don't understand what you mean by "switch to the Windows build"? The behaviour is system independent. Updating an index removes the structure and rebuilds it. That's why the cursor (when it is set inside of the index) is set to the beginning of the index and the view moves.
Comment 5 Oliver Specht 2004-06-09 07:22:28 UTC
according to the announcement on releases (http://www.openoffice.org/servlets/ReadMsg?list=releases&msgNo=7503) this issue will be re-targeted to OOo Later.
Comment 6 lendo 2009-03-13 13:30:50 UTC
These unexpected jumps are bad usability. Any chance to have a look at this in 3.x timeframe?