theme manager: fix path to assets for PyInstaller on POSIX systems #1191
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.
Avoid referencing the assets directory as relative to the
customtkinter/windows/widgets/theme
, which does not exist in PyInstaller-frozen applications due to python modules being collected into executable-embedded archive.Relative referencing from non-existant directories, such as
customtkinter/windows/widgets/theme/../../../assets
does not work on POSIX systems (Linux and macOS) and results in file-not-found errors even though the actual target directory (customtkinter/assets
) and its contents exist.Instead, resolve the top-level
customtkinter
directoy and its assets sub-directory via the pattern that is found in other parts of the code (i.e., useos.dirname
to jump to parent directories from__file__
location).