darktable-org / darktable-org/darktable
Module Layouts - Quick Access Entries Double
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
Whenever you open the Manage Module Layouts window, every entry in the Quick Access section adds another instance of itself (1>2>4>8 etc).
Steps to reproduce
- Open Manage Module Layouts window
- Turn on the Quick Access panel
- Add any module parameter
- Close Manage Module Layouts window
- Re-open Manage Module Layouts window
Expected behavior
Not change the Quick Access panel at all until manually adding an entry
Logfile | Screenshot | Screencast
Commit
Darktable nightly build 20251127
Where did you obtain darktable from?
darktable.org / GitHub release
darktable version
darktable-5.3.0+937.g323ff0234d
What OS are you using?
Windows
What is the version of your OS?
Windows 11
Describe your system
N/A
Are you using OpenCL GPU in darktable?
None
If yes, what is the GPU card and driver?
No response
Please provide additional context if applicable. You can attach files too, but might need to rename to .txt or .zip
I didn't make a note of the version that I first noticed this happening, but I know it was the version recommended on Reddit to use, and open all files that used AgX to make sure they would be correctly supported on official release.
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 the Manage Module Layouts window using the listed steps, then trace the Quick Access entries as the window is closed and reopened. Done means reopening the window no longer duplicates existing entries, while manually adding an entry still works; no source file or test is named in the report.
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
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100