Removing UASes now returns the UI to an almost pristine state. This was done by altering the activeUASSet signal so that it can emit a NULL UAS. Crashes may still exist in autopilot-specific code.

Partway through refactoring of UAS deletion. This is in order to actually support removing UASes from QGC, which is currently impossible.

Removing UASes now returns the UI to an almost pristine state. This was done by altering the activeUASSet signal so that it can emit a NULL UAS. Crashes may still exist in autopilot-specific code.

Partway through refactoring of UAS deletion. This is in order to actually support removing UASes from QGC, which is currently impossible.

Impl. Lorenz suggestions wrt one velocityChanged, altitudeChanged, speedChanged signal per reference frame. Impl. CDI on compass disk.

Fix for static const float cannot be initialized within a class definition, and other windows compile errors.

Hotfix: Fixed widget / UAS initialization order which led to text messages (and other updates) being ignored if the widget was not open when the UAS was created

Changes for new calibration in APM 3.0 (Re: https://github.com/diydrones/MissionPlanner/issues/38), and change in some of the serial timeouts

Change so Waypoints are the same across maps, and offline waypoints get appeneded to the end of the MAV's waypoint list on connect

Fix for crash when removing item from QuickView, and addition of more generic signal/slot combonation for property updates

This commit still allows configuration widgets to be loaded from qgc files
assuming that there is no APM generated xml file (arduplane.pdef.xml) in
the files/%autopilorname%/ directory. This filename needs to be
configurable, and selectable at runtime. It is not yet.

The right click menu will only show up when connected to an APM autopilot,
since this feature is APM only.

This will be removed once APM updates to support MAVLink
parameters properly.