Bug 400736

Summary: undo history should be more informative and hyperlinked
Product: [Applications] kdenlive Reporter: Adam Spiers <kde-bugs>
Component: Timeline & EditingAssignee: Jean-Baptiste Mardelle <jb>
Status: RESOLVED FIXED    
Severity: wishlist CC: fritzibaby
Priority: NOR Flags: fritzibaby: Brainstorm+
Version First Reported In: 18.04.3   
Target Milestone: ---   
Platform: Other   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:

Description Adam Spiers 2018-11-06 12:08:29 UTC 
Currently the undo history shows a very vague list of events, such as "Enable effect" or "Resize clip end".  This makes it quite hard to find a specific event in a long list of events.  There are several ways in which this could be improved.  Implementing any one of these would make things significantly better, but the combination of all of them would be a quantum leap in usability of this window:

- Add an extra column showing the exact wall-clock time when the event occurred.  This would make it easy to do things like "undo all edits made since 11.30am".

- Each event should reference the specific clip / effect / other objects with which it is associated.

- Right-clicking on an event could jump to the UI element representing the object which that event modified.  For example, right-clicking "Enable effect" would focus the clip for which the effect was enabled, and right-clicking "Resize clip end" would focus the clip being resized, moving the playhead to the new end of the clip.

SOFTWARE VERSIONS

kdenlive version: 18.04.3
KDE Plasma version: 5.12.5
Qt version: 5.9.4
Comment 1 Jean-Baptiste Mardelle 2024-01-11 18:23:15 UTC 
It took some time, but I finally implemented the timestamp in undo history:
https://invent.kde.org/multimedia/kdenlive/-/commit/bcffeef34eb6bcdd79fa9ce515e2490128c70cf4
Comment 2 emohr 2024-10-26 11:48:01 UTC 
I think with the latest Kdenlive version 24.08.2 all your 3 points are implemented.

I closed this bug. If it still appears in the latest version, please feel free to re-open it and update the affected version number.