| Summary: | Drying Ink Feature | ||
|---|---|---|---|
| Product: | LibreOffice | Reporter: | wichtigste_adresse |
| Component: | LibreOffice | Assignee: | Not Assigned <libreoffice-bugs> |
| Status: | RESOLVED WONTFIX | ||
| Severity: | enhancement | CC: | libreoffice-ux-advise, thomas.lendo |
| Priority: | medium | Keywords: | needsUXEval |
| Version: | 6.0.6.2 release | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
| Crash report or crash signature: | Regression By: | ||
| Bug Depends on: | |||
| Bug Blocks: | 107247 | ||
|
Description
wichtigste_adresse
2020-02-16 11:31:33 UTC
I'm open to be ideas and thinking and in favor of confirming an issue it would ever be beneficial to group of users. But not at the cost of disrupting basic functions. This would complicate ubiquitous use of text processor, to have text. And this is achievable with separate function of track changes. Not as handy as drying ink, but sufficient enough to show dates. Actually, I reported a bug long ago to make it easier to change user name in LO in order to have different changes. So in addition to simple changes with single user, where you can see dates, you could change user names and set some modes or moods or weather or whatever. (In reply to wichtigste_adresse from comment #0) > like it used to be with drying ink on a piece of paper or parchment... If you read ancient parchments but me has to organize the desk. Older papers go to the drawer, recent to the top etc. And while your example might be not perfect I can follow the idea of a timestamp when the addition/change was made. And perhaps the versioning is what you are looking for [1]. However, do not use it now. It has many issues (see bug 107247), in particular everything is saved not just the difference. [1] https://help.libreoffice.org/6.4/en-US/text/shared/guide/redlining_versions.html?DbPAR=SHARED#bm_id3154230 Excuse me, Heiko, but you put New, why, for what exactly to be done and how? (In reply to Timur from comment #3) > Excuse me, Heiko, but you put New, why, for what exactly to be done and how? Confirming the request and to keep the valuable use case; eventually we should change the summary. The topic was on the agenda of the design meeting but didn't receive further input. And actually we do have such a feature with the versioning (File > version), which saves a full copy with every save operation. Not ideal, admitted, but no need for another feature. |