https://bugs.documentfoundation.org/show_bug.cgi?id=129167

--- Comment #17 from Mike Kaganski <[email protected]> ---
(In reply to Roland Hughes from comment #16)

Sigh.
1. Roland Hughes writes in comment 0:

> Prior to updating to 6.3.3.2 whenever I reopened a book I was working on the
> cursor would automatically reposition to its last place. This no longer 
> happens
> and the keyboard shortcut no longer works.

We read a regression report here; so indeed, what is requested is to restore
*what was already working*.

2. Roland Hughes writes in comment 3:

> The restoring of last position used to work with both docx and odt. Now it
> appears to only be working with odt.

We read here, that Roland Hughes wants their docx behave like odt. Regardless
of the "it used to work with docx" delusion, the request is not "make something
different".

Now take a look at the LibreOffice code, where it restores the last position,
and learn that it is implemented (from the start) to store that information in
the ODT. Using a very simple logic, the request in this bug 129167 is exactly
"implement storing last position inside docx".

And yes, since the format is a MS format, we can't just start extending it
randomly without any need, we should stick to what MS used to store sch a
position.

3. Roland Hughes writes in comment 11:

> Saving a bookmark in the file itself would mean one could copy the file to any
> other machine with LO and have it open to the same line/col position.

The already mentioned delusion surfaces again. There was never anything like
what Roland Hughes describes *in LibreOffice* (or in any other OOo derivative).
So obviously, Roland Hughes *intended* to ask something different from what
they *actually* asked. So *this* report was created in a wrong way, and was
misleading from the start; in its current form, it is *exactly* duplicate of
bug 112740, while what Roland Hughes intended to request needs to be filed
separately (just because trying to rectify the initial mistake would not make
the request clear - it's best to start from scratch).

4. Roland Hughes writes in comment 16:

> Implementing "last one in wins" is short sighted and an architectural flaw.

Here they show how little they try to think about different needs. They think
about working in teams on the same file (a reasonable use case, even though
there is a different solution exist for that case, like Collabora Online, but
still having something "local" for that might be still reasonable); but they
just don't even ask "what is the use case for that feature that we declare
short sighted", they simply go ahead and declare. Well, of course, being able
to pick up working on *my* document at the point where I left, *regardless* of
which device I use at this moment (and thus, regardless of which user profile I
use at this moment) has no value for anyone, they perfectly know that.

MS may abandon their approach of storing the last position using the bookmark -
because they simply move to the cloud, and the last position may be restored
wherever you open the document. But LibreOffice has no central cloud. It is not
intended to push users to cloud. And thus, the storing of the last position in
the document is perfectly reasonable for a large portion of the user base, and
that doesn't exclude a potential option for a user to choose where to store
that - *if* Roland Hughes decides to file their feature request properly.

-- 
You are receiving this mail because:
You are the assignee for the bug.

Reply via email to