Now the user can release and grab the gripper while the UAV has
motors armed with the action button and also while the motors are
disarmed in a specific toolbar option.
Resolve of mavlink#10666, while the QGC window is resizing, both virtual
joysticks are not centered causing dangerous behavior. Now, if the screen
size is changed, both joysticks will be centered while the screen resize
is stopped.
In the edge scenario where we set video view in full screen
and for some reason QGC brings us to setup view ( if the
vehicle has calibration/setup pending ) the toolbar would
dissapear, thus not being able to get out of that state
All this remote id feature depends on a device being detected
so it makes sense to not show the rest of the flags until
a healthy connection has been detected.
Also change label from RID COMMS to NOT CONNECTED when there is
no RID connection, so it is more descriptive to the user.
TimeToHome fact calculates the time in seconds till the UAV reaches the
home position. We take the distance to home and divide it by the
current ground speed to get the seconds till we arrive at the home
point. I did not add any fancy logic to find out if we actually fly
towards the home point or are in RTL so the value shows increasing
seconds even if we fly away from the home point
Selecting terrain data on surverys was generating an empty survey if the polygon
was on an area where QGC doesn't have terrain height info about.
This is because QGC was waiting on terrain info to build the path on such surveys,
which is not needed at all, because terrain frame just specifies an altitude above
terrain, and relies on the vehicle for being able to calculate that height, by terrain
database or by altitude sensors, having terrain height information is not needed at all
to generate this kind of surveys
This fixes the warning that I get with GCC 11.3:
/usr/include/x86_64-linux-gnu/bits/string_fortified.h:95:34:
warning: ‘__builtin_strncpy’ writing 50 bytes into a region of size 24 overflows the destination [-Wstringop-overflow=]
95 | return __builtin___strncpy_chk (__dest, __src, __len,
| ^
/usr/include/x86_64-linux-gnu/bits/string_fortified.h: In member function ‘_handleStatusText’:
../Qt/5.15.2/gcc_64/include/QtCore/qarraydata.h:129:8: note: destination object ‘<anonymous>’ of size 24
129 | struct QTypedArrayData
| ^
Signed-off-by: Julian Oes <julian@oes.ch>
* Popup smaller
* Text indicates these are Vehicle Messages
* If there are additional messages which come in after display closing the popup will dropdown the Message Indicator in the toolbar
Status text messages were being sent too early in the creation of the MockLink. This would cause the ui to not see them. Making the whole thing useless for testing.
The current implementation displays two different distances by the same
name. One of the distances is actually the distance to the previous
waypoint. For the user its "hard" to tell which one is which. I try to
resolve this with a more descriptive label for the distance to the
previous waypoint.
An alternative is maybe to rename the other distance to total distance
or total mission distance.
Peter Barker
Sergii Lisovenko
PX4BuildBot
Don Gagne
DieBorr
davidsastresas
Philipp Borgers
Roman Dvořák
Julian Oes
Harsh Mittal
Don Gagne
jnomikos
Patrick José Pereira
Nick Exton
Sergii Lisovenko