The map scale width changes when the zoom up/down buttons are clicked.
When buttons are on the right, and when the user quickly clicks a zoom
up/down button several times, the first click change the scale, which
changes the buttons position. Subsequent clicks are most of the time not
where the user wanted to put them.
Putting buttons on the left of the scale will keep them at a fixed
position, fixing this unfortunate behavior.
Signed-off-by: Julien Olivain <ju.o@free.fr>
Ultimately it sends a MAV_CMD_DO_CHANGE_SPEED in meters
per second, so it is clearer if we have this name for the
function, could help avoiding confusion in the future
Previously the FlyViewMap only checked center tool insets to determine
whether to recenter the vehicle. This change makes it also check if the
vehicle has passed under a corner element using the corner tool insets.
This means the view will recenter if the vehicle flys under the
instrument panel for example.
This commit adds support for setting home clicking on map.
It is shown as another action in the submenu when we click
over the map with an active vehicle online.
As per mavlink specs, this command must use AMSL altitude,
so we need to first query terrain altitude, and when received
send the command.
Several checks have been implemented, and in case terrain
altitude is not shown at the selected location a popup will
appear indicating there are no terrain data for the specified location
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.
People wants to usue fullscreen without some text on the mididle of the screen,
10 seconds is enough to get the message.
Signed-off-by: Patrick José Pereira <patrickelectric@gmail.com>
It receives mavlink message obstacle_distance and shows distances in a circular array fashion.
Added a setting in Safety/Object Detection section to show the overlay.
Can be used independently to collision prevention features.
There are two overlays: Video and Map overlay
In different styles.
The styles could be changed in particular qml file.
https://github.com/mavlink/qgroundcontrol/issues/7670
Under some basemaps the default alpha value
for this panel was too transparent for the
user to see clearly the values. This commit
makes this alpha channel variable by a
setting under appsetings