Command+Z is acting erratic and is not reverting to the prior state. I've experienced it undoing several recent changes but also jumping to random layers. Is there a bug? Can you please advise?
I have not updated PhotoShop since 2017 so I was shocked to see the “command Z” undo has been changed to multiple undos going back 5, 10 or more steps. This seems to me as an unwanted change since the history palette already offers this service with text descriptions of exactly what is being undone.
I have always used command z as a before/after toggle to evaluate the edit I just made. I’ve tried for several months to adjust to the “command z” / “shift command z” functionality of the new version but it just far too awkward.
Is there any way I can restore the undo to a simple before after toggle? Thank you, --rick
I have not updated PhotoShop since 2017 so I was shocked to see the “command Z” undo has been changed to multiple undos going back 5, 10 or more steps.
It is a bug that Undo is jumping back multiple steps, but it was fixed in 24.1.1. Can you tell us (exactly) what version you have? (Help > About)
Before engineering fixed the bug, the interim workaround was to roll back to an earlier version.
The "legacy shortcuts" means that Cmd+Z toggles between undo/redo instead of giving us multiple undos. I don't know if that is a workaround, but the bug has been fixed.
So, the real question is... why are we constantly updating photoshop to work worse?
The question only you can answer. For many of us, it's for new features and fixes, and updating does work better. But you do know you can disable updates, right?
Author “Color Management for Photographers" & "Photoshop CC Color Management/pluralsight"
I am so tired with the unending stream of updates and often wonder the same question. I blame it all on subscription pricing. Adobe feels they must keep pushing updates to justify the monthly fee. It does not matter to them if the changes are of any value/benefit. If they returned to one time purchase, they would be forced to make the update compelling enough for people to WANT to purchase it.
Elements isn't the same, and you know it. Why do people continuously go to bat to defend a company that constantly objectively puts out unstable updates? Telling people to turn off updates (which defeats the purpose of paying for a subscription) or to downgrade to a lesser program is rididculous. And the fact that we have to come into a forum for help and get told to just reset our preferences or roll back yet again is infuriating especially when this is our livelihood. We can't just simply jump to another set of programs because Adobe has such a strangehold on the industry. Using a "if you don't like it, you can leave" mentality when it's the company's fault for routinely pushing unstable software and people are seeking help doesn't help anyone.
Becasue you are being an ass to be honest. I am pretty sure the goal is not to push unstable product but rather listen to the users and try to improve it. I was part of the PS Beta testers for years and with a program this complex, there is only so much that can be found before release. Expecting it to be perfect without any bug I am sure is the goal but its just not realistic so the next best thing is having a support group like this where suggestions, fixes and worarounds are offered almost immediately. Considering this is what I do for a living, I will take it vs the disaster that Quark Express and Painter were back in the late 90s with a too bad so sad mentality.
Where did I say it was the same? Perhaps this is a better fit for you. If not, then you have a few options:
Stick with the PS subscription; update, don't update, roll back to older versions.
Turning off updates for a period of time doesn't defeat the purpose of subscriptions! The software still runs; you can still use it.
Your call.
I'm not here to make decisions for you. I'm a volunteer here to provide support and options.
Some Adobe customers hate two things: Change and the way things are. 🤔
The bug reported last year was fixed. If you have other issues, or your version isn't working as it should with History, start a NEW bug report with all the necessary information: