forked from pcdshub/typhos
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request pcdshub#563 from klauer/enh_oneline_positioner
ENH: layout changes for compact complex screens + row positioner widget
- Loading branch information
Showing
19 changed files
with
2,009 additions
and
260 deletions.
There are no files selected for viewing
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
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
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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,50 @@ | ||
563 row-positioner | ||
################## | ||
|
||
API Changes | ||
----------- | ||
- ``TyphosNoteEdit`` now supports ``.add_device()`` like other typhos widgets. | ||
This is alongside its original ``setup_data`` API. | ||
- ``TyphosDeviceDisplay`` composite heuristics have been removed in favor of | ||
simpler methods, described in the features section. | ||
|
||
Features | ||
-------- | ||
- ``TyphosNoteEdit`` is now a ``TyphosBase`` object and is accessible in the Qt | ||
designer. | ||
- Added new designable widget ``TyphosPositionerRowWidget``. This compact | ||
positioner widget makes dense motor-heavy screens much more space efficient. | ||
- The layout method for ``TyphosDeviceDisplay`` has changed. For large device trees, | ||
it now favors showing the compact "embedded" screens over detailed screens. The order | ||
of priority is now as follows: | ||
- For top-level devices (e.g., ``at2l0``), the template load priority is as follows: | ||
|
||
* Happi-defined values (``"detailed_screen"``, ``embedded_screen"``, ``"engineering_screen"``) | ||
* Device-specific screens, if available (named as ``ClassNameHere.detailed.ui``) | ||
* The detailed tree, if the device has sub-devices | ||
* The default templates | ||
|
||
- For nested displays in a device tree, sub-device (e.g., ``at2l0.blade_01``) | ||
template load priority is as follows: | ||
|
||
* Device-specific screens, if available (named as ``ClassNameHere.embedded.ui``) | ||
* The detailed tree, if the device has sub-devices | ||
* The default templates (``embedded_screen.ui``) | ||
|
||
Bugfixes | ||
-------- | ||
- For devices which do not require keyword arguments to instantiate, the typhos | ||
CLI will no longer require an empty dictionary. That is, ``$ typhos | ||
ophyd.sim.SynAxis[]`` is equivalent to ``$ typhos ophyd.sim.SynAxis[{}]``. | ||
As before, ophyd's required "name" keyword argument is filled in by typhos by | ||
default. | ||
|
||
|
||
Maintenance | ||
----------- | ||
- N/A | ||
|
||
Contributors | ||
------------ | ||
- klauer | ||
- ZLLentz |
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
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
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
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
Oops, something went wrong.