The old behaviour adjusts the takeoff altitude set by the user with a
slider to be higher than the minimum takeoff altitude as definied by the
param MIS_TAKEOFF_ALT. This can be very confusing (and dangerous) as the
slider to enter the altitude does not reflect that. It always goes from
0m to 100m.
For example: the param is set to 10m. Now the user can command a takeoff
and set the slider to 1.5m. The drone will then takeoff and climb to 10m
completely without warning
I don't think it makes much sense to magically change the user input
without feedback. Therefore, I removed the adjustment.
With this change the drone will just go to the altitude commanded by the
slider.
- cl : Command line error D8021 : invalid numeric argument '/Wno-missing-braces'
- ..\src\VehicleSetup\FirmwareUpgradeController.cc(29): fatal error C1083: Cannot open include file: 'zlib.h': No such file or directory
* 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
PX4BuildBot
DonLakeFlyer
WTPENGUIN
kistlin
heeplr
olliw42
AndKe
CUAVmengxiao
Julian Oes
Luiz Kressin
Patrick José Pereira
acxz
Don Gagne
Don Gagne
Ljung323
Hunter522
Beat Küng
Philipp Borgers