iNavFlight
Break up HUD elements into individual OSD elements
Breaks up hud elements as individual OSD elements to allow different layouts to show/hide those elements.
This needs testing, as there may be side effects due to the order elements are drawn. We still check for the crosshair to be there, are it has a call to osdHudClear
This also need mentioning in the Release notes, as osd_hud_homepoint and osd_hud_homing settings have been replaced by the equivalent OSD elements and osd_hud_radar/wp_disp no longer control INAV Radar element visibility in the HUD.
I am curious to see how this would work with the hud clearing happening in the crosshair, and the drawing of the individual hud elements happening afterwards.
Due to the nature of how the drawing happens (by element id), the behavior should be similar, except that osdHudDrawHoming() used to happen before clearing hud, and now will happen after.
If there are side effects, we can move the individual elements back to the OSD_CROSSHAIRS case and just check if the individual elements are supposed to be displayed (like the first draft).
Is this still relevant? Has it been tested by someone other than the developer?
