"Undo failed due to programming error."

Question

I'm guessing this is undesirable action.  This occurred after taking a ctrl-z, which erroneously reverted a star rating --because the rating change was out of sequence of the undo steps.  In other words it got the undo steps mixed up while I was doing a sequence of ctrl-zs.   Better it did this than not say anything actually.  This is not really a "how to" type of question, just FYI.   If there are bugs in a any given program, I usually find them
P.S. I would guess it has to do with differently-rated or color-coded stacked virtual copies where the virtual copy is on top, and the sort is by rating, with filters on.  It seems to flash the screen around a lot when I use it as such and navigate around.
Message was edited by: George in Seattle

Answer 1

I'm wondering if this is really a bug or a design decision.
If you move the sliders the history does not update until you release the mouse button, as it should. Releasing the mouse button signifies you are finished with the adjustment.
Now consider the +/- keys. Each depression of the key moves the adjustment a fixed amount. My guess is that you would normally make several quick depressions of the key up,down or both until you are satisfied with the results. Do you want to record each and every key depression in the history or would you just like to have the end result logged in the history.
My choice would be to wait a finite amout of time between key strokes prior to logging in the history file which is what, I think, Lightroom is doing. What would be nice to have is a preference setting to control this inter-key depression timeout.
Cliff