Skip to content

Remove dead code in crop module #18847

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged

Conversation

jenshannoschwalm
Copy link
Collaborator

At two code parts we tested for p->ratio_d == -2 && p->ratio_n == -2. Reading the code and trying to understand these tests and if() actions, it's simply a leftover from clipping module while we stripped down that code. There it was used for a version bump enforcing recalculation of the ratio.

At two code parts we tested for `p->ratio_d == -2 && p->ratio_n == -2`.
Reading the code and trying to understand these tests and if() actions,
it's simply a leftover from clipping module while we stripped down that code.
There it was used for a version bump enforcing recalculation of the ratio.
@TurboGit TurboGit modified the milestones: 5.2, 5.4 May 21, 2025
@TurboGit TurboGit added the scope: codebase making darktable source code easier to manage label May 21, 2025
@TurboGit
Copy link
Member

This seems safe for 5.2, but maybe we can wait for 5.4. What's your take on this?

@jenshannoschwalm
Copy link
Collaborator Author

I actually don't mind :-)

@jenshannoschwalm jenshannoschwalm merged commit 8956c16 into darktable-org:master May 30, 2025
6 checks passed
@TurboGit
Copy link
Member

Ok, merged actually but no big deal.

@TurboGit TurboGit modified the milestones: 5.4, 5.2 May 30, 2025
@jenshannoschwalm jenshannoschwalm deleted the dead_crop_code branch June 2, 2025 09:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
scope: codebase making darktable source code easier to manage
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants