Skip to content
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

add alert to hazeremoval if HQ processing is disabled #18387

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

ralfbrown
Copy link
Collaborator

Candidate for addressing #18384.

The module's gui_update() function doesn't ever seem to be called, so right now the alert message's visibility is only set when first opening the image in darkroom.

@ralfbrown ralfbrown added the scope: UI user interface and interactions label Feb 9, 2025
@KarlMagnusLarsson
Copy link

HQ processing does not faithfully reproduce darkroom in darktable export result file when hazeremoval module is used.

One example is this case; https://discuss.pixls.us/t/color-management-issue-for-specific-image/46940. Even with HQ processing enabled there are differences between what is rendered and what is exported.

@TurboGit
Copy link
Member

@ralfbrown : gui_update() is called when entering darkroom to initialize the module UI indeed you may want to add the same code in gui_changed() which will be called for every slider changed in GUI.

@TurboGit TurboGit added this to the 5.2 milestone Feb 10, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
scope: UI user interface and interactions
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants