FR: Styles module: Add option to suppress preview#20255
FR: Styles module: Add option to suppress preview#20255TurboGit merged 15 commits intodarktable-org:masterfrom
Conversation
|
Do you know that if you turn off tooltips the previews wont display? |
Yes, I am aware of that. This was also suggested on pixls.us. But then, also the information about the modules involved in the preset is no longer shown. Furthermore, this affects all tooltips, which may not be desirable. |
I think I would store it. If a user goes to the effort to turn it off, then I think they expect it to stay off until they turn it back on. Tested and it works fine. |
Ok, you convinced me. I added storing the last state. |
|
And as we are at it, why not use a combobox with 3 options:
The "small preview" being what we have today. The "no preview" your proposal here, and "large preview" to have a larger preview as being asked in pixlus. |
|
@TurboGit Yes, why not, I am looking into it. Do you have a suggestion what the best size for large would be? I think the current size for the preview is 250. Maybe 500? Or make it a setting in darktablerc? I would not add it as a preference on the UI, though. |
Yes I would say between 400 & 500 I suppose. Let's start with 500 and will adjust the setting if needed. |
|
@deekayhd : Also the GitLab-CI failed because of an ambiguous code: You probably meant:
STYLE: Note the spaces around |
Aah, forgot the parenthesis, sorry. |
|
Thank you for merging. |
|
added PR #840 for enhancement of documentation. |


This pull request is a solution proposal for the feature request #20176.
The tooltip of a style in the styles module in lighttable view contains a preview of the style applied to the selected image. Especially, on computers without a GPU it may take some time until the preview is rendered and shown. During this time the UI is non-reacting. This is especially annoying when accidentally hovering over a style while moving the mouse.
This pull request introduces a new toggle to switch off the preview.
The default setting of the new toggle is TRUE, so that the current default behaviour is not changed. Also, the state of the switch is not stored; it will be set again in a new darktable session.
I am aware of the discussion about guidelines for the suggestion of new features. This feature request originated from a discussion on pixls.us linked in the corresponding issue #20176. I am not sure if there is already any consensus about a new guideline, but since this is only a minor change, I thought that providing a PR does not harm.
closes #20176