Description: Text cursor is at position P. From the menu Tools, I choose Update and hit on Update everything. When update finishes, the cursor is no longer at P and instead at the position of the last item in the document which needed to be updated (for instance, a final index of terms). Steps to Reproduce: 1. Set text cursor at some position P. 2. Choose Tools > Update > Everything. 3. Wait for Update to finish. Actual Results: After finishing, the text cursor is a the last item of the document that contained a reference field. Expected Results: The cursor should be at P. Reproducible: Always User Profile Reset: No OpenGL enabled: Yes Additional Info: Like my previous report on autorecovery not running in the background, this bug, too, is a (although unnecessary) consequence of LO programming not making use of threads. If it did, updating references would run in the background, letting me continue to work in the text. (And then, the menu option Tools > Update would not even be needed, because updating fields and references would continually be running in a separate background thread.)
I can't confirm with Version: 6.1.4.2 (x64) Build-ID: 9d0f32d1f0b509096fd65e0d4bec26ddd1938fd3 CPU-Threads: 4; BS: Windows 10.0; UI-Render: Standard; Gebietsschema: de-DE (de_DE); Calc: group threaded
Thank you for reporting the bug. I can not reproduce this bug in Version: 6.3.0.0.alpha0+ Build ID: 3c964980da07892a02d5ac721d80558c459532d0 CPU threads: 2; OS: Windows 6.1; UI render: default; VCL: win; TinderBox: Win-x86@42, Branch:master, Time: 2018-12-12_02:07:45 Locale: en-US (en_US); UI-Language: en-US Calc: threaded and Version: 6.1.3.2 Build ID: 86daf60bf00efa86ad547e59e09d6bb77c699acb CPU threads: 2; OS: Windows 6.1; UI render: default; Locale: en-US (en_US); Calc: group threaded
Created attachment 148341 [details] Screen video showing updating of all references As the video shows, the cursor is on a chapter heading before triggering the process and at the beginning of the terms index after it.
Can you please attach the document, so that I can test it again. Please do remove any sensitive information from the document if you have any.
There is no practicable way to generate a version of this document that could be made publicly available, as it is a book manuscript to be published soon. However, I would like to put it at your disposal, and more generally, at the disposal of the developers community, since it is a large document suitable for testing some other improvable features of LO Writer. So please give me an address where to send the file.
Durgapriyanka shared the document with me. Fortunately, we do not need it (or prepare some anonymised version), because I found an existing older report. *** This bug has been marked as a duplicate of bug 38738 ***