Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Enquable Hardware UI/functionality #197

Open
ksunden opened this issue Nov 9, 2018 · 0 comments
Open

Enquable Hardware UI/functionality #197

ksunden opened this issue Nov 9, 2018 · 0 comments
Labels
bluesky These issues are handled by bluesky

Comments

@ksunden
Copy link
Member

ksunden commented Nov 9, 2018

Currently a rudimentary implementation of setting hardware in queue is included and works, though there are several things to be considered as it moves forward:

  • Currently there is no checking of units or preventing you from assigning nonsensical (or even nonexistant) units in the UI
    • Consider using drop down menus to limit choices, hide UI elements that result in "illegal" operations.
    • Consider including a "Kind" drop down and only showing hardware associated with the selected units kind (and thus only the units that are for that kind as well)
  • Currently only a single value is used per line item, meaning if you wish to set 5 hardwares to different positions, you need to enqueue 5 separate items.
    • This makes things like returning to a particular system configuration less user friendly
    • Conversely, this makes the UI simpler (and potentially less ambiguous, though updates needed to achieve that)
    • If we go the route of setting multiple at once, UIs to borrow from:
      • the Scan UI, with only one value field, but with buttons to add different kinds
      • the hardware sidebar, without the "current" field, and with check boxes to activate each

It has also been expressed that things like OPA shutters should be accessible, which they currently are not.

@ksunden ksunden added the bluesky These issues are handled by bluesky label Jul 16, 2020
ksunden added a commit that referenced this issue Aug 10, 2021
See #247 #197

This is a quick and dirty way of being able to do 'chopping' like data workup on Waldo...
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bluesky These issues are handled by bluesky
Projects
None yet
Development

No branches or pull requests

1 participant