Skip to content

Dont access button variables directly#5

Open
zaped212 wants to merge 1 commit intosweddavid178:mainfrom
zaped212:2026_button_changes
Open

Dont access button variables directly#5
zaped212 wants to merge 1 commit intosweddavid178:mainfrom
zaped212:2026_button_changes

Conversation

@zaped212
Copy link
Copy Markdown

Creates new functions Btn*Held to be used instead of accessing the variable directly.

This should help reduce confusion seen by the students trying to determine the difference between:
joystick.BtnXPressed()
vs
joystick.BtnX

Existing Btns have been converted to private to the class.

Creates new functions Btn*Held to be used instead of accessing the
variable directly.

This should help reduce confusion seen by the students trying to
determine the difference between:
joystick.BtnXPressed()
vs
joystick.BtnX

Existing Btns have been converted to private to the class.
@zaped212
Copy link
Copy Markdown
Author

I haven't had a chance to test this out on a rover yet, but did a find replace and believe I covered all existing usage.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant