Doesn’t have a done key which doesn’t work with our user model. May
find a better fix later.

All qsTr calls done

Signed-off-by: Tomaz Canabrava <tomaz.canabrava@intel.com>

All facts are numeric, atm. this means that the input should only
accept numbers. it already had the     inputMethodHints:   Qt.ImhFormattedNumbersOnly
option, but for some reason it still accepted letters and symbols.
by adding a     validator: DoubleValidator {} we limit the characters
to numbers only - and if the value is a integer, it will still work.

Tested by adding waypoints on the map & messing with the GPS coordinates.

Signed-off-by: Tomaz Canabrava <tomaz.canabrava@intel.com>

Map control use different border color based on map type

Total hack but it seems to work

There are many ways of iterating over lists in C++/Qt.
In the specific case of QStrings, it is known [1] that using
foreach with const references avoids the creation of new
QString objects in each iteration, reducing the time consumed
by the loops.

[1] https://blog.qt.io/blog/2009/01/23/iterating-efficiently/



Signed-off-by: Anselmo L. S. Melo <anselmo.melo@intel.com>

Instead us a Toolbox concept which hangs off of QGCApplication

- MultiVehicleManager is a Qml friendly replacement for UASManager
- Vehicle is a replacement for both UAS and AutoPilotPlugin

If Facts are referenced from FactPanelController, we need to reference
count the AutoPilotPlugin such that it doesn’t get destroyed until
after the FactPanelController is destroyed.

Passing parameters QVariantMap across C++ boundary was causing crashes
in Qt due to Qml array bugs. Referencing same Fact* across Qml boundary
in multiple QQuickWidgets caused jScript GC to crash.