Enhanced Undo/Redo for better keyboard shortcut support
ImplementedHello,
I work with keyboard shortcuts a lot (Exposure +1 and so on), in particular with external devices providing actual knobs which I can turn back/forth, which are then translated into keyboard-shortcuts (similar to Tangent / Loupedeck...)
If I try that out (+/- exposure, and so on) and decide that I want the original value before turning the knob there is no way for me to get back to the value.
I could press Ctrl-Z for a long time but I would go past the point of exposure changes and come into various other UNDOs. That is totally unmanageable... There is also no global history list, where I can just click on the first entry with exposure changes.
I could think of one of the following possibilities which would make working with shortcuts and undo/redo much better (prioritized by usefulness)
- Ability to create and restore an undo/redo "snapshot" via keyboard shortcut.
That would mean one can create the snapshot, then do all of the exposure +/- (as many times as one wants) and then if one wants to get back to before, just restore the "snapshot" via keyboard shortcut. I think there would normally also be no need for multiple snapshots, one would be sufficiant.
- A global preference setting one could activate, that would allow Capture One to store UNDOs/REDOs aggregated by target value. Meaning, that if I repeat the same operation 5 times (5 times expose + to continue my example) it would only store 1x undo, but with the intensity 5 times. So that when setting exposure +1 for the first time, there is no difference to the current version of C1. When setting +1 a second time it would look in the undo (is the last operation the same, if so don't add an aditional undo but use the existing entry and increase it's value). And if I were to use exposure -1 it would lookup the last undo operation and see that the target value exposure is also effected and update that too instead of storing a new entry for exposure +.
That would help much, as one would then only have to undo onces (instead of 30-50 times and not knowing when to stop).
- If 1 or 2 are too big a change for C1 development, than please at least provide the possibility to clear the entire UNDO/REDO history via a keyboard shortcut (just as if one were to close and open C1). That would be the cheapest version of a "snapshot" if you so will. But it would at least be useful... I would think that this should be very very easy to implement...
Thanks a lot in advance for considering!
-
Hi there,
Thank you for your feedback on Capture One - we appreciate the time you've taken to contribute towards the development of the software.
I have forwarded your comments and suggestions on to our Product Management team as something to consider in a future release. Hopefully, your feedback contributes towards a future version of Capture One.
Though we cannot comment on future releases and the features to be added, we recommend keeping an eye on this article - click Follow next to the title of the article to stay up to date with new features and improvements.0 -
Thank you! I had another idea (variant 4), if you so will.
What would also work: if everything was the same as now, but two additional commands (triggerable via keyboards shortcuts) that perform additive "undo/redos", automatically repeating undo/redo if the stored command is identical.
Let's say you have 15 times Exposure + and 13 Times Exposure -
Then that special additive undo or redo would execute all commands which are the same in a sequence. Undo and undo and undo until it sees, that it's no longer Exposure + and it stops. Then only the 13 Exposure - are left. And one executing of another undo would trigger those (same) commands. And so on.0 -
Hi
I am having a problem logging on to my laptop with capture 1. I need to open it on my laptop and then use it on my desktop so I can see properly. I think I am entitled to do that as I can use it on 2 devices. please can you help, as all my images are on my laptop. Urgent.
Thanks
Thanks
0 -
Hello Valerie, I think you need to open a new issue, since this has nothing to do with my undo/redo feature request ;)
0
Post is closed for comments.
Comments
4 comments