Have settings loaded/stored correctly for all joysticks based on their UAS type and autopilot type. Switching between UASes doesn't work right yet, however.

Changed many functions in the abstract *Link classes to be const. This facilitates setting other functions as const. The metadata for specific links are reset when the links are added.

The details on the success/errors for the MAVLink protocols are now shown for each link as tooltips that are updated every 5s. Values are currently wrong and unsure why as of yet.

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

Changed many functions in the abstract *Link classes to be const. This facilitates setting other functions as const. The metadata for specific links are reset when the links are added.

The details on the success/errors for the MAVLink protocols are now shown for each link as tooltips that are updated every 5s. Values are currently wrong and unsure why as of yet.

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

HIL config improvements, fixed confusion about which dock widget is part of which view, main window behaving now

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

Addition of requesting status updates from APM, if APM is in a state with no status updates, this will request them

The reason for this is, because the last change in the file structure is buggy, it was only written the message length of the buffer to the file and missed to add the length for the timestamp.
For fixing this problem it would be possible to insert something like

len += sizeof(quint64);

after:

int len = mavlink_msg_to_send_buffer(buf+sizeof(quint64), &message);

But I think a consistent file structure has more adavatages for a logfile over a more compressed structure.
E.g. it would be necessary to go through all packages to proceed a jump during a replay.
Additional the LogPlayer was not updated during the last 7 month since the logfile structure was changed (even it was buggy)...

If filesize is really a problem I would recommend to change the logfile handling in a way of writting a temporary consistend
logfile and compress it afterwards (QCompress) like done by many programs

First stab at JSBSim interface, compiling, operational, but needs the correct startup folders and arguments

fix hardcoded start of fgfs and terrasync, use system environment variables for linux distro independence