There are currently two ways to press the function keys - one in keyboard.py ("press f four") and one in nav2.py ("f four").
I think that we shouldn't have both and we should just keep the keyboard.py one. Neither are currently CCR. The F keys in nav2 do not appear to be documented anywhere.
A breaking change as users would now have to say "press f4" rather than just "f4".
How Has This Been Tested
Trivial enough
Types of changes
[x] Breaking change (fix or feature that would cause existing functionality to change)
Checklist
[x] I have read the CONTRIBUTING document.
[x] My code follows the code style of this project.
[x] I have checked that my code does not duplicate functionality elsewhere in Caster.
[x] My code implements all the features I wish to merge in this pull request.
[ ] My change requires a change to the documentation.
[ ] I have added tests to cover my changes.
[ ] All new and existing tests pass.
Maintainer/Reviewer Checklist
[x] Basic functionality has been tested and works as claimed.
Remove f keys from nav2.py
Description
All in the title
Related Issue
None.
Motivation and Context
There are currently two ways to press the function keys - one in keyboard.py ("press f four") and one in nav2.py ("f four").
I think that we shouldn't have both and we should just keep the keyboard.py one. Neither are currently CCR. The F keys in nav2 do not appear to be documented anywhere.
A breaking change as users would now have to say "press f4" rather than just "f4".
How Has This Been Tested
Trivial enough
Types of changes
Checklist
Maintainer/Reviewer Checklist