Fix Plan save message on exit

Signed-off-by: Patrick José Pereira <patrickelectric@gmail.com>

Signed-off-by: Patrick José Pereira <patrickelectric@gmail.com>

Signed-off-by: Patrick José Pereira <patrickelectric@gmail.com>

Enable/Disable based on fixed base position

Add support for specifying fixed RTK base position

Added support for qgcRebootRequired Fact meta data value.

Prevent clicks going through top level items

Fixed the core MAVLink receiver. Among other things, it wasn't accounting for fragmented messages.
Fixed code that monitors messages received (and lost)
Added a section within the MAVLink panel to show the current status (for the current vehicle)
Remove some old, unused exposed interfaces

Add new Help page under Settings

Signed-off-by: Patrick José Pereira <patrickelectric@gmail.com>

Add test for an existing window before attempting to close it.

Show the link indicator in the tool bar if two or more links are connected and at least one of them is a high latency link.
Show in the link indicator if a link is inactive.

- Improve function names
- For notifications of an active link change only show the priority keyword if multiple links are connected
- Use QMap instead of QList for the HeartbeatTimers
- Style improvements
- Simplify sending the MAV_CMD_CONTROL_HIGH_LATENCY command

This setting enables/disables the LinkIndicator toolbar in which the primary link can be chosen.

The LinkIndicator shows the connected links and lets the user select the priority link,

Automated preflight checklist: Initial commit. Note that this requires an autopilot firmware that writes the respective health flags in the SYS_STATUS mavlink message

Signed-off-by: Patrick José Pereira <patrickelectric@gmail.com>

Try/Finally causes window to close all the time

Cleaning up old vehicle manager and getting it ready to actually provide services for a vehicle (flight management)
Added submit flight plan
Added update flight plan
Disable flight features as these don't seem to be quite working (values must be initialized and validated before submission as backend doesn't validate and the objects don't initialize their members)

Signed-off-by: Patrick José Pereira <patrickelectric@gmail.com>

Create a "Dead Mouse Area" control to eat mouse events underneath desired area. This is to prevent mouse events from leaking through controls underneath the area.
Replace original "NoMouseThroughRectangle" as this is more versatile.
Prevent mouse through events from leaking underneath the Fly View tool strip.