- if gstreamer is not found but Microhard or Taisync is enabled
issue an error message and cancel CMake generation
- exclude the target_link_libraries call if Microhard or Taisync
is not enabled
- if Microhard or Taisync is enabled add compile definitions to
enable #defines in the source code, else there are build errors
Sliders with a non 0 minimum value have this
issue where the default minimum is 0, so if
setting a new minimum value changes, and thus
we have an onValueChanged, setting the value
of the slider to minimum even before
onCompleted, so if they need to be initialized
to something it doesn't work.
This commit fixes it setting a bool variable
so onValueChanged doesn't take effect until
initialized
Any signals or events which do significant work (including deleting objects marked with `deleteLater()`) may cause segmentation faults or use-after-free errors.
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.
kistlin
PX4BuildBot
DonLakeFlyer
Pierre Abbat
Patrick José Pereira
Daniel Agar
alexklimaj
davidsastresas
Keith Bennett
WTPENGUIN
Don Gagne
heeplr
olliw42
AndKe
CUAVmengxiao
Julian Oes