Skip to content

Explicitly set non running scripts to FALSE #430

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
merged 1 commit into from
Sep 20, 2023

Conversation

wpferguson
Copy link
Member

Explicitly set non running scripts to FALSE instead of relying on no value being interpreted as false.

This prevents a reoccurrence of darktable-org/darktable#15280

Fixes #429

                           instead of relying on no value being intrepreted
                           as false.
@wpferguson wpferguson changed the title Explicitly set non running scriopts to FALSE Explicitly set non running scripts to FALSE Sep 20, 2023
@wpferguson wpferguson merged commit 014a0fc into darktable-org:master Sep 20, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

script_manager: explicitly set run state of scripts
1 participant