https://bugs.documentfoundation.org/show_bug.cgi?id=112740
--- Comment #4 from Roland Hughes <rol...@logikalsolutions.com> --- (In reply to Justin L from comment #3) > Of course, care needs to be taken to delete any existing _GoBack bookmarks > while doing this. And of course no point in saving this if LO can't read it > back first. > > See bug 112742 comment 3 for info on how ODT imports this info. Exporting is > likely done via xmloff/source/core/xmlexp.cxx ImplExportStyles. > > Exporting ViewSettings in DOCX is docxexport WriteSettings(). The point I was making in the other bug marked as duplicate of this one is that I don't believe the last position was ever saved in the document. The reason for this belief is I use a lot of machines between my office and home. Store many/most of my important documents on a NAS. At least the important ones I'm currently working on. I fill in all of the contact information for LO in my account on each machine. Back when this worked for both, it didn't work across machines. If I spent the day in my office editing something and saved it before going in for supper then opened the same document on the same NAS with my laptop from within the house, it didn't go back to the same line on my laptop. If my laptop had opened it before, then it went back to the same line the laptop remembered. This operated as if the document and last position were being stored in an INI/Settings type file specific to each user on each machine. There as probably some failure to clean up (how could LO ever know you were really done?) which lead to some kind of size/performance issue parsing that file(s). Were I to guess, that would be my guess. It is based on behavior I observed. Were it stored in the document I would have always returned to the last position no matter which machine. Storing in the document also opens up a major can of worms. Fred spends the morning working on pages 123-152. He saves the document with is cursor in the middle of page 151. Sally spend a couple of hours after lunch working in the same document file on the same NAS. Her edits are in the page range of 41-54. She exits and saves with cursor in first position of page 54. Jill spends a couple of hours working on the document in the evening using the exact same file on the exact same NAS. She started adding pages at 184 and got on a roll. The document is now 248 pages long. When she saves and exits the cursor is in the dead last position of the file. Which one wins? If you are storing the file and last position locally per user in a Settings/INI/etc. file, the feature behaves __exactly__ as each user expects. When they open the file up the cursor goes right back to their personal last known position. If you store it as a bookmark in the file, last one in wins and two other users file bug reports about last position being broken. -- You are receiving this mail because: You are the assignee for the bug.
