Skip to content

Conversation

@mmosca
Copy link
Collaborator

@mmosca mmosca commented Jul 27, 2023

Break up hud elements as individual HUD elements so they can be turned on/off by selecting a different OSD profile.

@mmosca
Copy link
Collaborator Author

mmosca commented Jul 27, 2023

Haven't tested yet, but should make it easier to test iNavFlight/inav#9199

@mmosca mmosca changed the title HUD refactor Break up HUD elements into individual OSD elements (configurator changes) Jul 27, 2023
@mmosca
Copy link
Collaborator Author

mmosca commented Jul 27, 2023

#1808 is related to this, as it groups the HUD settings together, to match the hud elements layout of this pull request.

@mmosca
Copy link
Collaborator Author

mmosca commented Jul 27, 2023

This is what the new section will look like.
image

Potentially, the crosshair can be moved here as well.

@mmosca mmosca marked this pull request as ready for review July 27, 2023 17:25
@MrD-RC
Copy link
Member

MrD-RC commented Jul 27, 2023

I would probably change INAV Radar to ESP32 Radar / Formation Flight.

It hasn’t been called INAV Radar for a while.

@mmosca
Copy link
Collaborator Author

mmosca commented Jul 28, 2023

I would probably change INAV Radar to ESP32 Radar / Formation Flight.

It hasn’t been called INAV Radar for a while.

That is an easy change. What about changing it to MSP Radar? Now it is more about the protocol, as there will soon be 3 possible sources for this data. (ESP32, Formation Flight and ExpressLRS).

@mmosca
Copy link
Collaborator Author

mmosca commented Jul 28, 2023

Also, should we move the crosshairs to the HUD section so all related elements are grouped together?

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.

3 participants