BUG: allow for pydm to find pyside6 designer path, makes "Open in Designer" button work with pyside6 #1295
Conversation
This file contains hidden or 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
nstelter-slac
force-pushed
the
pyside6_designer_naming
branch
2 times, most recently
from
4d369ba to
df15ae0
Compare
nstelter-slac
force-pushed
the
pyside6_designer_naming
branch
2 times, most recently
from
3323f08 to
8756cb7
Compare
Designer" button work with pyside6 previously pyside6 pydm couldn't find the designer path, and this was b/c `QLibraryInfo.location(QLibraryInfo.PrefixPath)` (and therefore with the other QLibraryInfo enum values too) returns different paths on pyqt5 vs pyside6: pyqt5: /home/nolan/miniforge3/envs/pydm-environment-pyqt5/ pyside6: /home/nolan/miniforge3/envs/pydm-environment-pyside6/lib/python3.13/site-packages/PySide6/Qt/ taking a closer look into an example pyside6 conda-env, there seems to be two copies of the qt6 designer: "/home/nolan/miniforge3/envs/pydm-environment-pyside6/lib/python3.13/site-packages/PySide6/designer", and "/home/nolan/miniforge3/envs/pydm-environment-pyside6/bin/designer6" these don't seem to be simlinks, and can both launch a version 6.9.2 of designer so with PySide6 easiest way to grab a designer bin location might be just to remove "Qt/" from the end of the result-string from "QLibraryInfo.location(QLibraryInfo.PrefixPath)". The qt6 designer in this location is just named 'designer', which avoids having to handle the 'pyside6-designer' vs 'designer6' naming diff on conda vs pip installs.
nstelter-slac
force-pushed
the
pyside6_designer_naming
branch
from
8756cb7 to
db01ba3
Compare
jbellister-slac
approved these changes
Oct 3, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
previously pyside6 pydm couldn't find the designer path,
and this was b/c
QLibraryInfo.location(QLibraryInfo.PrefixPath)(and therefore with the other QLibraryInfo enum values too) returns different paths on pyqt5 vs pyside6:pyqt5:
/home/nolan/miniforge3/envs/pydm-environment-pyqt5/pyside6:
/home/nolan/miniforge3/envs/pydm-environment-pyside6/lib/python3.13/site-packages/PySide6/Qt/taking a closer look into an example pyside6 conda-env, there seems to be two copies of the qt6 designer:
/home/nolan/miniforge3/envs/pydm-environment-pyside6/lib/python3.13/site-packages/PySide6/designer, and/home/nolan/miniforge3/envs/pydm-environment-pyside6/bin/designer6these don't seem to be simlinks, and can both launch a version 6.9.2 of designer
so with PySide6 easiest way to grab a designer bin location might be just to remove "Qt/" from the end of the result-string from
QLibraryInfo.location(QLibraryInfo.PrefixPath). Also,the qt6 designer in this location is just named 'designer', which avoids having to handle the 'pyside6-designer' vs 'designer6' naming diff on conda vs pip installs.