darktable-org / darktable-org/darktable
Copy history stack does not copy over lens correction settings
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 13.1k
- Forks
- 1.4k
- Avg merge
- 22h 14m
- Merged PRs (30d)
- 198
Description
Is there an existing issue for this?
- I checked and did not find my issue in the already reported ones
Describe the bug
When I use the 'copy hiistory stack' feature on a photo that has lens correction module enabled and paste in over to another photo, it does not enable 'lens correction' for this file.
Steps to reproduce
- go to lightable
- select and open a photo
- enable lens correction
- go back to lightable
- select this file and click on history stack -> copy
- select a different file
- click on history stack -> copy
- the second file will not have lens correction module enabled
Expected behavior
the second file should have lens correction module enabled
Logfile | Screenshot | Screencast
No response
Commit
No response
Where did you obtain darktable from?
distro packaging
darktable version
5.4.1
What OS are you using?
Linux
What is the version of your OS?
debian stable
Describe your system
No response
Are you using OpenCL GPU in darktable?
No
If yes, what is the GPU card and driver?
Please provide additional context if applicable. You can attach files too, but might need to rename to .txt or .zip
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the issue in darktable 5.4.1 by enabling lens correction on one photo, copying its history stack, and applying it to another photo. Start by tracing the history-stack copy and paste flow alongside lens correction module activation; done means the destination photo has lens correction enabled after the stack is applied.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- desktop
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100