ES-Alexander

> Thinking about Barometer, yes, it probably does make sense to have that too, and eventually deprecate this. This may not be the right place to bring this up, but...

The most relevant UI element I can think of is a gradient/vignette around the screen edges, with a center (and possibly rotation) that adjusts depending on the motion being represented....

Relevant to #1525.

It feels a little too dev-focused/debuggy for that to me... It could maybe be changed to some kind of icons, and/or have a description of what it's for, but as...

[Current `MANUAL_CONTROL` motion handling](https://github.com/ArduPilot/ardupilot/blob/master/ArduSub/joystick.cpp#L53) works by converting to RC overrides. This would likely be handled better by a more general abstraction (as above), but if the RC overrides conversion is...

- MAVLink `MANUAL_CONTROL` support was updated to 32 buttons and 6 motion axes in #25671 - The message now also includes 6 auxiliary axes, but they are not yet mapped...

@dgudiel mentioned the appearance of this isn't super consistent with other parts of the interface. The suggested alternative is to add stability chips (e.g. "stable", "beta", "dev"), like GitHub's version...

> Need to ... check if the new parameter is configured in storage before setting it. @IamPete1 I may be misunderstanding, but both functions already check the existing servo channel...

- `k_shift` could be handled by the GCS, instead of discarding the option for button combinations - `k_camera_source_toggle` seems like not the autopilot's jurisdiction - most likely it should also...

Relevant to #3501