Handle locked state in hardware widgets
A disabled
state is provided to the hardware widget. It's an aggregation of multiple states like operator
.
This PR mostly add the locked
state from the hardware to this disabled
widget state.
As result a locked hardware is disabled by default.
Some more care was provided to the motor state cause it's the only use case i have right now.
One down fall of this approach is for example for a motor which lock itself during it's motion.
- As result for now we have to allow the user to stop it -> Which also also the user to stop the rotation motion during a scan. This could be discussed.
- The locked state have to be updated at the same rate of the others properties (1s), else the motor stays locked few time at the end of the motion (until the locking state is refreshed by daiquiri). Tested with an update every 5s.
Edited by Valentin Valls