Skip to content

toneEQ: move exposure/contrast compensation sliders to advanced tab #18682

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

Open
wants to merge 2 commits into
base: master
Choose a base branch
from

Conversation

MStraeten
Copy link
Collaborator

since there're endless discussions on tweaking the tone equalizer a lowest common denominator might be simply moving the controls for mask exposure and contrast compensation to the advanced tab. since the real estate of the gui is driven by the simple tab, the additional required vertical space is taken from the graph and in masking tab there's unused space. the bar indication the spread of the histogram on masking tab is no longer needed, so removed

…vanced tab

since there're endless discussions on tweaking the tone equalizer a lowest common denominator might be simply moving the controls for mask exposure and contrast compensation to the advanced tab.
since the real estate of the gui is driven by the simple tab, the additional required vertical space is taken from the graph and in masking tab there's unused space.
the bar indication the spread of the histogram on masking tab is no longer needed, so removed
@jenshannoschwalm
Copy link
Collaborator

tested just now:

  1. There is a UI gap in the masking tab -
    Bildschirmfoto vom 2025-04-13 16-37-49

as this is missing :-)
Bildschirmfoto vom 2025-04-13 16-42-04

  1. Not sure - shouldn't mask quantization be in the advanced tab too?

@MStraeten
Copy link
Collaborator Author

the gap is there because the minimum height of the module is determined by the sliders in simple tab.
Mask quantisation results can't be seen in the histogram graph - so it seems to be better to keep it on masking tab.
also the graph will be compressed further, if there's a further slider put on advanced graph.

the histogram representing mask bar is no longer used, since the effect of the moved sliders can be seen directly in the histogram.

@elstoc elstoc added the documentation-pending a documentation work is required label Apr 14, 2025
added the UI/UX change
@marc-fouquet
Copy link
Contributor

Obviously I don't have anything working right now on my PR. Even though I haven't given up just yet, it looks like my stuff will take a lot longer.

Just for inspiration, I wanted to show what my current UI looks like, after all the discussions in that forum thread.

2024-04-18

I went for a version, where the histogram is always visible and the tabs are placed below it. This is useful, because smoothing changes the histogram too, which is immediately visible here. I also put almost everything into collapsible sections, so people cen decide for themselves, how much vertical space they want to use.

Regarding mask quantization: I don't think that this is an option that should be placed in a prominent location. I don't think that this is widely used, I regard it as an unsuccessful attempt to have a little bit of zone system in the module.

@MStraeten MStraeten requested a review from TurboGit April 19, 2025 06:33
@MStraeten
Copy link
Collaborator Author

This pr keeps the vertical space needed for the module, since there’re users running darktable on capable notebooks where screen size is limited.
this pr doesn’t want to change the UX fundamentally but is improving the users workflow in a often demanded way.

@da-phil
Copy link
Contributor

da-phil commented Apr 21, 2025

Changes are looking fine for me.
Because folks have been talking about how precious vertical space was to them I wanted to ask how you feel about removing the x-axis labels of the node UI, see framed in red:
Screenshot from 2025-04-21 16-06-17

IHMO there is no real usage for it, only the y-axis labels are. However they are probably still helpful to cross-reference the sliders in the simple tab.

@MStraeten
Copy link
Collaborator Author

This pr isn’t intended to be a major change of the toneequalizer UI - so no further changes beside what’s needed to optimize the handling of the mask histogram.
There are plenty of non converging discussions on the UX of tone equalizer - so let’s keep this pr small and without scope creepers …

@TurboGit
Copy link
Member

TurboGit commented May 3, 2025

@MStraeten : You may want to try out #18656 (be ware that this will break all your ToneEQ presets). I think #18656 is the way to go, the auto-fit is especially fixing a itch I had for this module.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation-pending a documentation work is required
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants