Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Implement robot subsystem state indicators and communication state indicators. Include ifndefs/ifdefs for different robots/robot types #86

Open
n-speed opened this issue Jul 7, 2024 · 0 comments
Open

Implement robot subsystem state indicators and communication state indicators. Include ifndefs/ifdefs for different robots/robot types #86

n-speed opened this issue Jul 7, 2024 · 0 comments
Assignees
@n-speed @zDagger
Labels
codebase feature Feature to be developed that can be applied to the whole codebase

Comments

@n-speed
Copy link
Member

n-speed commented Jul 7, 2024

ClientDisplaySubystem needs multiple subsystem calls to current robot states such as chassis pose (IMU) and if CV detects a target.

Including ifdefs to define which subsystems to call and draw to the client also need to be applied.
@n-speed n-speed added the codebase feature Feature to be developed that can be applied to the whole codebase label Jul 7, 2024
@n-speed n-speed moved this to 🏗 In progress in Texas Aimbots Software Management Jul 7, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@n-speed n-speed

@zDagger zDagger

Labels
codebase feature Feature to be developed that can be applied to the whole codebase
Projects
Texas Aimbots Software Management
Status: 🏗 In progress
Milestone
No milestone
Development

When branches are created from issues, their pull requests are automatically linked.

features/updated_ui_investigation_24 TAMU-Robomasters/aimbots-dev
2 participants
@n-speed @zDagger