Skip to main content
W
Wolfgang Lienbacher
Inspiring
October 19, 2025
Question

The last done edit is not Copy and Pasted if done with Keyboard or SDK API

  • October 19, 2025
  • 1 reply
  • 319 views

When I hover with mouse above a Slider, and use the Keyboard up/down arrows to adjust its value, and once happy with the value press Cmd+C, confirm the fields to be copied by pressing Ok, move to the next image and press Cmd+V, all Settings of the previous image are copied, except the last made change with the Keyboard. 

 

The isse is identical if I use a plugin to change the value. Like the Elgato Streamdeck Plugin by SideshowFX, that makes a call to the SDK function LrDevelopController.increment(key) or LrDevelopController.setValue(key, value) to change the value. The behaviour is exactly the same. The last value is not copied, but the value done one step earlier is. For instance, if I adjust Temperature, and then Brightness, followed by a Copy+Paste action, the Brightness value change will be ignored, but the Temperature change will be copied. 

 

If I however use the mouse to make the Change by using the Slider, Copy and Paste works as expected. 

 

This is a Bug that has been present and plagueing me since I'm rather certain Lightroom V1 from 2007. For me, it is the most annyoing and time killing Bug that I am personally facing in Lightroom. It triggers me every single time I use lightroom since 18 years. 

 

I'm finally taking my time to file a bug report, because I've come to accept this bug wont ever magically disappear. I'd be forever greatful if this bug would finally get tackled. Lightroom would be so much more fun to use, If I didn't constantly have to go back and forth images repeating Copy and Paste action because the last done edit hasn't been taken, or proactively do weird combo key presses to avoid this happening, because this bug is really really present in my mind when I'm editing. It's really a huge rock blocking my otherwise very speed workflow, and it's been there since so many years. 

1 reply

johnrellis
johnrellis
Legend
October 19, 2025

Hmm, I'm not observing that in my LR 14.5.1 / Mac OS 15.7.1, when I follow these precise steps (see the attached screen recording):

 

1. Click on the first photo in the filmstrip.

 

2. Hover the mouse over over the Temp slider.

 

3. Use the up-arrow key to increase Temp.

 

4. Hover the mouse over the Exposure slider.

 

5. Use the down-arrow key to decrease Exposure.

 

6. Type Cmd + C to open Copy Settings and observe that Basic is already selected.

 

7. Type Return to close Copy Settings.

 

8. Used Cmd + right-arrow to move to the next photo in the filmstrip.

 

9. Type Cmd + V to paste the settings. Observe that the values for Temp, Tint, and Exposure from the previous photo are correctly pasted into the current photo.

 

I get the same correct results if I use the mouse to click on the Copy button in step 7 and use the mouse to move to the next photo in step 8.   

 

1.  Do you see the misbehavior when you do these exact steps? 

 

2. Do Help > System Info. What are the exact version numbers of LR and Mac OS you're currently running?

 

Unless Adobe can easily reproduce the problem, they're not going to pay much attention, unfortunately.

 

 

W
Wolfgang LienbacherAuthor
Inspiring
October 20, 2025

Hey John, 

thanks for following up. I've made a screen recording as well. Indeed, on the first try after I read your post it did not happen, I went ahead and tried again: it happened. In the screen recording I am attaching it's happening most of the time, but not every time. 

 

I am running LR 14.5.1 and mac os 15.6.1, but as I said: this is not a new issue, it's been haunting me since the very very early days of LR, and I've been using it since V1.0. I am honestly puzzled this is not a known thing because I'd put my hand in fire: I do not remember any time this has not been plaguing me, and I'm having a very hard time to imagine it's only me. I am pretty sure this an issue that has it's core in some lower level code of the LR UI that has been untouched ever since it was released. 

W
Wolfgang LienbacherAuthor
Inspiring
October 20, 2025

I just called a colleague and was able to confirm: on his windows machine it does not happen, but on his mac he is able to confirm the problem. 

Terms & ConditionsAccessibility statement
Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices