Skip to content

Conversation

@jenshannoschwalm
Copy link
Collaborator

In a lot of cases we report "YES"/"NO" or "TRUE"/"FALSE", introduce two macros for code density.
Second commit makes use of those

In a lot of cases we report "YES"/"NO" or "TRUE"/"FALSE", introduce two macros for code density
@jenshannoschwalm jenshannoschwalm added the scope: codebase making darktable source code easier to manage label Jan 12, 2026
@jenshannoschwalm jenshannoschwalm added this to the 5.6 milestone Jan 12, 2026
@TurboGit
Copy link
Member

I was about to propose that while reading your previous PR. Nice!

@jenshannoschwalm
Copy link
Collaborator Author

@TurboGit is is possible to cherry pick and merge at least the first commit introducing the macros now?

@jenshannoschwalm jenshannoschwalm force-pushed the alternative_simple_yesno branch from 03aedca to eab66dd Compare January 13, 2026 07:41
Using `STR_TRUEFALSE` and `STR_YESNO`
- consequently use the nts dt_print() variant for better formatting
- avoid showing build logs if there isn't any or too long
@jenshannoschwalm jenshannoschwalm force-pushed the alternative_simple_yesno branch from eab66dd to acf3748 Compare January 13, 2026 10:33
@jenshannoschwalm
Copy link
Collaborator Author

Added all opencl related log changes to this PR ...

@TurboGit
Copy link
Member

@TurboGit is is possible to cherry pick and merge at least the first commit introducing the macros now?

Yes I can do that.

@jenshannoschwalm
Copy link
Collaborator Author

Yes I can do that.

I reworked the different PR's a bit and now here is all related logging stuff. So no need to do so ...

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