Rework executable path handling #489
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
executable_manager can see new executables in
case they need the user to find the path and
assign it. Reworked check_if_bin_exists to
use the preference if it exists to try and
cut down on the "flickering windows" problem
on windows.
enhancements in the file library so
that executable paths can be assigned
to new executables that they system was
unable to detect.
|
Depends on darktable-org/darktable#17300 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Updated executable path preferences so that executable_manager doesn't have to read the darktablerc file to get the executables and paths.
Changed check_if_bin_exists to use preferences first. This should cut down on "flickering windows" on windows