showLabel was connected to signal but not set as a slot

There is no such things as a clicked signal on QWidget. You activate
new UAS from right-click menu.

ui->waitingLabel is deleted and set to NULL when mode is PX4. Must
check for NULL before using it.

The connect call was generating debug output to identify that it was
failing. After looking at the code realized that this connect is not
needed. The group box is removed when UASListWidget::removeUAS method
is called.

Second change in the file fixes a crashing bug when the last UAS is
removed. Need to exit the iterator after we modify it.

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.

Also fixed some code in QGCPX4VehicleConfig to remove unnecessary DialogBare references.

Added documentation and clarified messages to the user.

This feature can be enabled at compile-time and documentation has been added to the README.

Now properly checks for if QUpgrade submodule has been cloned.
Allows for disabled QUpgrade compilation.
Altered some code so that compiling without the QUpgrade module could
succeed.
Updated README about QUpgrade submodule.

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)

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.