UNDO problems need attention soon
I have been looking this up for awhile now and every time there's an upgrade, I hope it's resolved, but it hasn't been, yet. The forum topics I have found are mostly from people working with Sessions, which I do not. I have both large and small catalogs and have cmd+z issues in both. And, I have also found that it has been reported in many previous version, but I have always been able to cmd+z as many steps as I needed to get back as far as I wanted.
At this time, cmd+z will rarely undo anything I have just done, except take me back to another frame I left many frames ago, and loses everything I just did on the frame that I was actually working on. I do not have custom shortcuts and never messed with them so I guess I have always used the defaults.
I decided to create another post in this topic because it doesn't seem to be getting any attention. This really needs to be addressed, especially with CO21 about to be released. It is force of habit to hit cmd+z when I don't like something. It's bad enough that CO20 doesn't have a history list to retrace steps, but for undo to be defective is practically unusable. I like my workspace to be trial and error, which is impossible to pull off if you can't undo anything and have to manually return settings to where they were, which is what I end up doing most of the time, which is extremely frustrating. I have seen many remedies for deleting plist files, deleting default shortcuts and reinstalling them, deleting custom shortcuts, restarting the app, etc etc etc, none of that holds up nor fits into my work flow. And, as I mentioned, most of these remedies are for Sessions, I typically only use catalogs.
If any of the developers or tech people follow the forum, I really do not want to go back to anything from that other software company, please get this bug resolved. I would really appreciate it. Transferring over 15k images back to the room would not make me happy, not at all. But I am also very unhappy now, please get this working again.
Thank you for your time.
Tech: Mac Pro 2013, Catalina
*Edit: I did 'submit a request' on this topic. :)
-
Hi,
With me, cmd+Z undo the last operation, and I can reverse the history, suppressing last operations one after the other, pressing cmd+Z as many times as I wish.
0 -
Yes sometimes it works like that (as it should) but then it randomly stops working. If I am uncertain about what will happen if I use Cmd-Z on any particular occasion, I go to the Undo command in the menu. If it says "Undo White balance" or whatever, I know I am good to go. If it says "Undo Selection" just after I change White Balance, then don't do it. Restarting the app usually sets it back to what it should do.
An annoying bug, for sure!
Ian
0 -
I have the same problem and have had it for at least the last couple of versions of C1. Cmd-Z backs up to a point and then just seems to toggle between two steps. As Ian says, I can go to the menu and see what C1 is going to undo, but that really defeats the purpose of having a keyboard shortcut.
A weirdness is that Undo behavior isn't reproducible. Sometimes it works fine, at least through the number of steps I care about, and sometimes it fails after a couple of steps.
I just live with it.
0 -
Been struggling along with the UNDO (cmd Z) function not working on both my Macs running Mojave and C1/20 (since Dec 2019). After submitting logs and a screen recording to tech support they came back to say that they were able to recreate the issue when using sessions and after a batch rename. I tested their theory and this seems to be the cause of the issue - Cmd Z works fine until the batch rename function is used, thereafter UNDO reverts to a previous folder (I think). The only quick fix is to restart C1, then it works until the next batch rename.
Would be interested to know if anyone else experiences this issue when batch renaming. The issue was reported to C1 over 6 months ago and although there has been an update since reporting it has still not been resolved. Shocking really that something so basic and such a staple of the editing process would be faulty and allowed to be rolled out. Wish Affinity would bring out an alternative to C1 and LR.
0 -
How does Affinity deal with the situation after a Batch rename?
Not something I have tried there.
0
Post ist für Kommentare geschlossen.
Kommentare
5 Kommentare