darktable-org / darktable-org/darktable
There should be a way to clean up disabled modules from history
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 13.1k
- Forks
- 1.4k
- Avg merge
- 22h 14m
- Merged PRs (30d)
- 198
Description
Is your feature request related to a problem? Please describe.
Currently once I'm done editing a photo it might still be full of modules that i toggled just to see how they might look then disabled, polluting the history of the file, even more of an issue if I want to copy that image's style to another photo and I'm seeing a bunch of modules which are not as useful (I have already opened an issue about the selective copy screen as well, so no need to delve into that part here).
Describe the solution you'd like
Add a button that removes all disabled modules from the history. I would prefer if compress history did this instead alongside its current features (considering removing misc unused modules does compress the history and it's already destructive in the way it removes entries) but I would be fine with a separate button as well.
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
No file, test, or entry point is named; start by locating the history controls and the existing compress-history behavior. Confirm how disabled modules are represented, then make the requested cleanup available through compression or a separate button, with completion shown by disabled modules no longer appearing in the image history.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- desktop
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100