Feature/#126 disable buttons during homing

[hello-william]

Description

Originally subtask in #60 but now moved to #126.

During homing, these buttonpads should be disabled:

ButtonPadButton.ArmLower
ButtonPadButton.ArmLift
ButtonPadButton.ArmExtend
ButtonPadButton.ArmRetract
ButtonPadButton.WristRotateIn
ButtonPadButton.WristRotateOut
ButtonPadButton.GripperOpen
ButtonPadButton.GripperClose

Testing procedure

• Turn "on" robot and it still needs to be homed.
• Ensure appropriate buttons are visually+functionally disabled.
• Home it!
• Ensure appropriate buttons have been enabled.

Before opening a pull request

From the top-level of this repository, run:

• pre-commit run --all-files

To merge

• Squash & Merge

[hello-william]

the styling for disabled is "meh" for now... just wanted to get the logic down

i'll test it tmrw morn on vy's robot

[hello-william]

@hello-binit PR is ready for review

[hello-binit]

@hello-william Could you include screenshots of how the UI should look?

[wle8300]

@hello-william Could you include screenshots of how the UI should look?

for sure!

the robot should be un-homed tmrw, so i'll grab screenshots of the UI before+after it's homed

[hello-william]

@hello-binit

hasn't been homed...

...homing...

...homed!

while buttons are disabled all hover+click events are also disabled

[hello-binit]

@hello-william looks like the docs from #124 are included in this PR. Do you want to rebase to only include your changes in this PR?

[hello-william]

@hello-binit ah sry about that... should be g2g 🏄‍♂️

[hello-robot-shehab]

fyi, I tested:

• Restarted Stretch -> launched interface -> tried the buttons, they are disabled, as expected. They look the same as the screenshot above.
• Homed using the button in the interface -> the buttons are now enabled, and work as expected.
• Restarted the robot -> homed using stretch_robot_home.py -> the robot is now homed -> launched the interface -> the buttons are enabled, as expected.

Code looks great. Thanks @hello-william!

[hello-binit]

Looks good to merge!

[hello-binit]

I've seen this check fail with this error before. We'll need to look into it. For now, bypassing the check and merging.

[hello-william]

@hello-binit

I've seen this check fail with this error before. We'll need to look into it. For now, bypassing the check and merging.

#45 actually solves this

once it's merged to master the pre-commit routine should go smoothly