MAVLink dialects can now be specified as a list, so multiple dialects can be compiled in simultaneously (may result in conflicts between dialects).
MAVLink dialects are checked for existance before support is added.
Users are notified of which dialects are used and which cannot be added and why.
The README now has info about specifying MAVLink dialects.

use getAcceptanceRadiusRecommendation function to set default radius based on airframe. With this commit airframe based radius setting now works for + button and double click in map and also for all waypoints (also the first one)

Enable RC calibration mode during RC calibration to tell vehicle to ignore stick inputs for that period

Always evaluated to false due to signed/unsigned

This allows us to create mock version of the objects to use for unit
tests

- NAN not available in windows headers, use cross platform friendly
version
- VS compiler does not allow initializing non-integral types in header
files
- ActiveQt libs are already installed by Win Qt4.8.5, no need to build.
Plus this part of the makefile just loops without nmake.exe installed
which is not part of a standard windows box

Altitude splitted to altitudeAMSL and altitudeRelative, speed splitted to airSpeed and groundSpeed. PrimaryFlightDisplay uses airSpeed for FW and groundSpeed for MC.

flightgear hil: correct scaling of pressure for mavlink message and remove indicated airspeed from flightgear protocol, commit requires flightgear protocol update

Replace 9 seperate valueChanged() signals with just 1, and remove the resultant tons of code duplication