fix(nix): fixup and rework, always use nixpkgs PySide/Qt #1048
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.
Summary
Depends: #1047Fixes: #915
Fixes: #988
Took me some time to completely work this out (and to get sorted from life stuff). The good part is that whatever issues were halting simply using the newer versions of PySide are seemingly no longer there. The wrapping done for Qt was fixed, it was not quite done correctly, which broke using hardware acceleration. Outside of that, this does some general touch ups to get to the state of the current repo.
To hopefully prevent future mismatches between the version of PySide, and therefore Qt, used in the project versus present in nixpkgs, I override where the PySide module from nixpkgs is always used, even in the dev shell. This is a trade-off from sticking to an environment closely resembling ideals, but managing the drift in versions clearly hasn't worked out. It might be worth checking out patching the dynamic library for Qt that PySide loads, but that might still have the issue of PySide's own version.
Tasks Completed