-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Robothat auto record on throttle #1055
Conversation
- port mode and recording latching code from joystick controller because auto-record on throttle was not working correctly with the robohat MM1.
- when throttle changes then latch the new recording state
- this was copied from joystick controller, but because robohat controller does not change mode, it is not needed.
I switched to the Yes, the It also did not record waypoints (records) when TCIII |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
@@ -149,13 +155,21 @@ def run_threaded(self, img_arr=None, mode=None, recording=None): | |||
""" | |||
self.img_arr = img_arr | |||
|
|||
# | |||
# enforce defaults if they are not none. | |||
# |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Probably accidental duplication of comments.
Address issue #1053
Robothat controller was not updated when we added code to make the game controllers and web controller cooperate. I ported the recording latching code to the robot hat controller.