Bug 333979 - Undo/Redo actions should always show which action is undone/redone
Summary: Undo/Redo actions should always show which action is undone/redone
Status: RESOLVED WORKSFORME
Alias: None
Product: okular
Classification: Applications
Component: general (show other bugs)
Version: 0.17.5
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: Okular developers
URL:
Keywords: triaged
Depends on:
Blocks:
 
Reported: 2014-04-27 22:58 UTC by Barade
Modified: 2018-10-27 02:17 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Barade 2014-04-27 22:58:37 UTC
When writing a popup note annotation and closing it and then calling the "undo" action, it removes parts of the text I wrote in the popup note (normal undo behaviour) but I do not get any feedback!
The popup note should be opened and it should be shown to me what is undone exactly.
I had a case where I did some actions afterwards and did not know until when I had to undo stuff or if it did affect anything because I got no feedback.

Reproducible: Always
Comment 1 Luigi Toscano 2014-05-08 16:50:40 UTC
In the latest version (0.19.x) Okular scrolls to the annotation when undo is performed. Opening the annotation is going to be complicated, as "close annotation" is not an action that can be undone (adding text is), so if the add texts to 3 annotations  (add text, close note, add text...), then undo and redo the three operation, you will have the 3 annotations open.
Would some additional visual feedback (in addition to the scroll) be enough?
Comment 2 Andrew Crouthamel 2018-09-25 03:48:59 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days, the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please set the bug status as REPORTED so that the KDE team knows that the bug is ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 3 Andrew Crouthamel 2018-10-27 02:17:00 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!