Use a pragma around our use of that header to silence the warning. OSG
3.01 has these warnings, 3.2 has fixed them, but 3.2 doesn’t isn’t the
widely used release yet. So at some point when we upgrade to 3.2 this
will no longer be needed.

Disable the active WP setting in the edit list, as its super error prone - only allow it in the view list and switch between views based on activity on the system / UI

Use a pragma around our use of that header to silence the warning. OSG
3.01 has these warnings, 3.2 has fixed them, but 3.2 doesn’t isn’t the
widely used release yet. So at some point when we upgrade to 3.2 this
will no longer be needed.

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)

Conflicts:
	src/comm/QGCFlightGearLink.cc

PX4 config: Remove the specialized throttle handling - this needs testing, but doing the math on paper it doesn’t look like a special case is needed / wanted here.

Use the reversed values for the four control channels as well. Not using them would make the display very confusing.

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

TeamCity caught this, but I thought the error was from my warnings
work. Turns out it was a real build failure. Windows doesn’t know which
floating point floor to use. In reality the parentheses are in the
wrong place and should be the floor of the divide by 2. But integer
division is always floor, so it’s not needed at all.