Skip to main content
Inspiring
November 17, 2012

P: Undo function fails and applies a preset instead

  • November 17, 2012
  • 51 replies
  • 1427 views

LR4.2 When removing a photo from a collection and then pressing "undo" the photo is not returned to the collection and instead a preset is applied to the next photo.

This topic has been closed for replies.

51 replies

Inspiring
April 14, 2014
Downloaded 5.4 and now ctrl+z launches a email module. This is worse because now I have to wait for it to compress images and open a pop up window! Does limiting the number of presets even matter now since its a different problem?
Participating Frequently
April 9, 2014
Hi All,

I have a temporary workaround for anyone who is hitting this problem very frequently. This bug happens because of the way that menus are built on Windows. It can conceivably happen in pretty much any situation, but it becomes much more likely to happen if you have a menu that contains a whole lot of items. The most likely way to end up with a menu that contains a whole lot of items is to have a lot of Develop presets (since there are some menus in Lightroom that will list every Develop preset you have). So, there are two ways to prevent this problem from happening (or to make it much less likely to happen):

1. Reduce the number of Develop presets that you have. Do you have 1,000 presets, but you really only use a dozen of them? Try removing the others temporarily.
2. Avoid using any menu that lists the Develop presets. This includes most of the menus you get when you right-click on an image (because they contain a "Develop Settings" submenu) and also the "Saved Preset" pop-up menu in the Quick Develop panel in Library.

Obviously neither of these workaround is very appealing, but if you're having this problem a lot, I wanted to give you something to try while we work on a fix. If you do try either of these workarounds, I'd be interested to know if it helps.

Thanks,
Ben
Participating Frequently
April 9, 2014
Responding to Trevis's question above, this bug is not fixed in 5.4 (sadly, 5.4 was locked and loaded before this issue was figured out).

-Ben
Participating Frequently
April 8, 2014
Would it be presumptuous of me to think that this 5.4 update that LR is notifying me about has this fix?
Inspiring
April 7, 2014
it does indeed suck as I have had this problem for over a year! 🙂 I think Adobe are sorting it now.
Inspiring
April 7, 2014
It has been occuring since today morning. Instead of going step backward it applies a certain preset. I am using LR 4.4.
It cannot be undone via EDIT - UNDO either, the only way to get to the preivous status is to go to Develop - History and select a status there.
It sucks,
Inspiring
April 3, 2014
Great news!
Inspiring
April 3, 2014
wooho sounds really awesome. 🙂
Inspiring
April 3, 2014
Great to hear Ben may be finding a fix, this is becoming an increasingly frustrating bug.
Legend
April 3, 2014
Hi Ben, thanks for being fastidious in tracking this down!