After fuirther tests, I realized that the boxes were preventing events
from propagating to the OSD elements, preventing the user from moving
them.
Now the boxes are transparento to events.
To me, this looks wrong. So I have left the calculated values in there, commented out.
I tested in the Avatar goggles with the camera set to 4:3. Then moved the guides to match. Unfortunately I don't have the correct adapter to take the USB out of the Avatar goggles and in to my FatShark HDO goggles (4:3). I will get hold of an adapter and re test. But this can be updated through a bugfix PR if necessary. I've also read that even if set to 4:3, the VRx/goggles still output 16:9. So it may even need a firmware update on the Walksnail side to get this 100% confirmed.
Folks didn't like the red button. They thought there was an error with the calibration. So I have changed the button to a subtle grey. Hovering changes red as a warning still.
- Moved to turn assist in to **flight mode modifiers** section. As it applies to fixed wing and multirotors.
- Re-established name changes for `CAMERA CONTROL` 1 to 3 when a RunCam Device is used.
This PR adds target autodetection to the firmware flasher. It will attempt an autodetect on load. Plus there is a manual button to autodetect by the description.
- Extended MSPHelper to collect the missing data sent in `MSP_BOARD_INFO`. Plus added a `getTarget()` function.
- Added target autodetect on load of Firmware Flasher.
- Added button to Firmware Flasher to command an autodetect.
- Toggling **Show unstable builds** now remembers the selected target.
- Fixed **Offline** notices in the board and version select boxes.
- Added target name to firmware version displayed when connected.
- Fixed issue where non-standard orders would not draw the output numbers.
- Added a refresh button to revert to current mixer after another mixer preset has been selected, but not loaded. This also has a prompt for assistance
- Fixed issue where changing the servo input would not update the outputs table.
First cut of code. It's pretty much there. I just need to decide how to handle changing the mixer type, then deciding to stick with the current mixer. Other than that, it's working as expected.
- Tidied up units label to work with more tabs
- Added more fields in the PID Tuning to use the highlighting
- Converted the Rates tab over to use data-i18n more. Will make sure all of the PIDs pages use it fully.
