P: Don't understand the undo/redo system

[FeedbackCommunityMember]

Unlike most modern apps, Photoshop only has a single "undo". If you press command-z a second time, Photoshop will redo the change instead of continuing to undo. Not even Illustrator or InDesign works this way at this point.

To work around this issue, I customize my keyboard shortcuts to use "step backward" (command-z) and "step forward" (command-shift-z). For the most part this works great and I've been very happy with it.

But it brings up a new problem: if I change the selected layer, then press command-z ("step backward") then the layer change is undone as well. This is a constant frustration for me, and it seems there's no solution to get both the behaviors I want.

To me, there are two possible ways to fix this problem:
• Adopt a standard undo/redo system with multiple levels of undo/redo
• Make layer selection a separate step in the history

Personally I don't care that much, I'd be happy with either. But adopting a standard undo/redo system makes more sense to me, for consistency amongst the CS apps (as well as other apps). Perhaps it could be an option if there's disagreement over what works best for people.

[yoyo34000]

I think that the best solution would just be to reprogram the stepbackward function.
Ideally, you could setup the things you want to have integrated into this stepbackward: brush strokes, layer selection, layer visibility, selecting a color, whatever.
A menu with boxes to thick or unthick would just be perfect and solve everyone's problem i guess.

[fruityth1ng]

Let's be frank, the fact that this is still an issue is EMBARRASSING. It's a stubborn headed non-response by *someone* at the photoshop team sticking to their guns, holding that this is the "correct" design. It is not, and people are noticing. I'm unfollowing this topic since it is hopeless, some designers' pride is taking prevalence over usability here. I'll just install the polycount script on every new release of photoshop. Like the "free artboard movement" tweaks that are needed with every new release, too. Adobe, you're making software for professionals, is the learning curve of photoshop really your main hurdle to more sales?

[Allen_W]

with that keyboard shortcut problem, what version of photoshop are you using?

[limandy444]

Hihi

[Allen_W]

what are the "free artboard movement" tweaks?

[limandy444]

Okok

[Allen_W]

the reason adobe has the default undo function designed the current way is to enable the user to easily toggle any new changes back-and-forth so the user can easily decide on changes. but this causes problems for users that need a more standard undo system--particularly for users such as painters and illustrators who make lots of brush strokes.

a better approach to the default undo system is to make it work more like "step backward" and give users single-key shortcuts for each undo and redo [such as press Z for undo and press X for redo]. this will maintain the convenience of toggling back and forth while simultaneously allowing the convenience of multiple undos and redos.

if adobe will ever make the default undo system work more like "step backward" as outlined above, perhaps adobe will have more incentive to fix this "wrong layer selection" problem.

[limandy444]

Hihi

[yoyo34000]

This does not really explain why they would remove the good old undo. They could have very well kept it and make this "before after" feature another single function (the "compare function").
It was then more straightforward, and avoiding this torrent of disappointed people 😛

[Smoothjunk]

I am constantly stepping backwards. One of my biggest gripes with PS is when you select a layer, mark the layer some how (with a brush stroke for example), then step backwards, it does not stay on the layer you selected, instead reverts back to the layer you were on previously. Please Adobe, revert the change made to the layer, not the layer selected prior to the mark. That is two actions in my opinion and should be treated as such.
Is this a known issue? Something Adobe is currently fixing? Am I making any sense?

[Allen_W]

this has been a major complaint for many years. but adobe has done nothing. if adobe can comment on this and say they will fix it in the next version, it would be awesome. but so far, no hope.

adobe seems to be more focussed on adding new features than to reexamine and improve workflow.

[Smoothjunk]

Not unlike most folks posting in this community, I use Photoshop more than any other program and have used it for going on 20 years, give or take a year.
There is one hangup I have that I constantly run into that bugs and frustrates me that I wish could be addressed. It seems to be a simple issue on the surface.
I tend to use dozens and dozens of layers when creating illustrations. If I select a layer to edit, make an edit to that layer then Step Backward (that is, I undo the change I made), Photoshop undoes the change and takes me back to the layer I was on before making the change. If I want to continue to work in the layer I selected, I have to find it again and, as most of you know, finding the layer again can be a bit time-consuming.
When I Step Backwards, I expect to undo the change I've made to the layer I am on and NOT undo the change *and* take me back to the previously-selected layer.

[Allen_W]

this problem is one of the big reasons why photoshop is not a drawing-friendly program.

[FeedbackCommunityMember]

Why does stepping backwards change what layer you're working on? Say I'm editing layer 2 and then switch to layer 3. Then I make two brush strokes on layer 3, and realize I don't like them. If I "step backward" twice, I'll be back on layer 2, even though I want to be working on layer 3. At best I have to annoyingly reselect layer 3, and at worst I might accidentally do work on the wrong layer. "Undo" is useless here because it bafflingly only ping-pongs between your last change.

Why on earth would it work this way? Why, at the very least, do we not have more options for either keeping layer selection immune from any changes or adding a layer change to history, so that in my above example, I'd have to "step backward" 3 times to be back on layer 2?

[J453]

See: https://helpx.adobe.com/photoshop/using/undo-history.html

In Photoshop CC (2015) update, step backwards shouldn't change the layer selection.

[DermotPower]

At last!!!?

[fruityth1ng]

Jeffrey, we've known each other for years through this topic. I for one will raise a glass tonight to this super-welcome feature. Thank you! 🙂 !

[DermotPower]

iPhone thumb fumble meant a limited reaction from me earlier... really happy that photoshop made this change - will make my life a lot easier from now on. Might have deserved a bit more fanfare!

[Allen_W]

i'm happy this will finally get fixed. but i wonder why it took so long--was it really that hard to fix?

btw, can we get an update to also fix it for Photoshop CS6? many of us are not ready to go CC yet.

[Smoothjunk]

This is amazing! This update will save me so much time per project. I will actually have to adjust my current workflow to adjust to this update -- adjust for the better, of course!

[DermotPower]

Gosh Kris you must be delighted Adobe have given the rest of us the special powers you have in your photoshop!!!!! Where is your sarcastic post about it?

[FeedbackCommunityMember]

Yes, it wasn't that simple to change. The originally stated problem is not a bug in any way, but the unintended side effect that people complain about is the selected layer changing. So we had to work around the layer change due to stepping back in history, along with safety logic to prevent it from selecting something that no longer exists.

No, older versions will not get new features.

[FeedbackCommunityMember]

Thank you (and possibly your teammates) so much for fixing this. A lot of artists (especially the ones who use a Wacom) are going to have a lot less frustration now!

[FeedbackCommunityMember]

Really glad about this!!! I'm the one who posted the image of the drawing in an earlier comment and post. This will save a lot of heartache and headaches!

[DermotPower]

I've read Chris Cox's reply several times and I've no clue what he's on about - guess it doesn't matter if the 'not bug' is fixed ...