* Draggable radius adjustment for Loiter mission items
* Revert usage of MainRootWindow activeVehicle
* Various changes to loiter visuals
- remove TerrainStatus loiter radius
- make loiter map visual dynamic
- use _planMasterController.controllerVehicle
- move some of the visibility logic out of QML to CPP
- get rid of placeholderMapCircle in FlyViewMap
This fixes a broken build on my setup. Otherwise I see the following
error:
/home/borgers/projects/qgroundcontrol/src/QtLocationPlugin/QGCTileCacheWorker.cpp:1200:79: error: use of ‘auto’ in lambda parameter declaration only available with ‘-std=c++14’ or ‘-std=gnu++14’
1200 | connect(socket, &QAbstractSocket::errorOccurred, this, [this, socket](auto error) {
|
As mentioned in https://github.com/mavlink/qgroundcontrol/pull/9591
* MockLink - Support REQUEST_MESSAGE:AUTOPILOT_VERSION, REQUEST_MESSAGE:PROTOCOL_VERSION
* Fix bugs in Vehicle::requestMessage
* Switch to all INT mission items
* Create unit tests to exercise Initial Connect state mache state failure conditions
Before this change it is not allowed to set up the flight modes unless
all sensor calibrations are completed.
I don't think that makes sense because it is possible to calibrate RC
without having the sensors calibrated, and it's the logical next step
right after that.
It is also a problem if HITL (hardware-in-the-loop) is used where the
sensors are not marked as calibrated but you still need to be able to
configure the flight modes. This is what prompted me to suggest this
change.
DonLakeFlyer
Don Gagne
Don Gagne
PX4BuildBot
Ljung323
Hunter522
Beat Küng
Philipp Borgers
Andrew C. Smith
numan.uyar
Julian Oes
Aleksey Kontsevich
Patrick José Pereira
Thies Lennart Alff