You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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:
It has also been expressed that things like OPA shutters should be accessible, which they currently are not.
The text was updated successfully, but these errors were encountered: