For some reason in mobile the button would keep as hovered
even if it is not pressed, so it was weird. This way it
makes more sense for mobile, the UI is consistent with
what is happening
For some reason in mobile the button would keep as hovered
even if it is not pressed, so it was weird. This way it
makes more sense for mobile, the UI is consistent with
what is happening
This defaults to the most obvious way to turn (shortest direction) from
commit Mission item: CONDITION_YAW - added shortest direction.
This behaviour when changing directions is what users are familiar with
from any simple mission flight (that RPAS turns the shortest way toward
the target)
This defaults to the most obvious way to turn (shortest direction) from
commit Mission item: CONDITION_YAW - added shortest direction.
This behaviour when changing directions is what users are familiar with
from any simple mission flight (that RPAS turns the shortest way toward
the target)
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>
This points the GPS/Drivers submodule to a commit in the qgc-4.3 branch,
just backporting the fix required to get F9P working.
Signed-off-by: Julian Oes <julian@oes.ch>
* User guide migration to QGC source
* Add google analytics - but need [GA4] Find your Google tag ID
* Update (most) notes to use vitepress note syntax
* Convert remaining notes, tips, warnings
* Prettier all the files
* Lower case and compress all images
* Lower case filenames
* docs_deploy1
* Disable platform builds on commit to docs (only)
* Test deployment script 1 (#10893)
* docs_deploy1
* Disable platform builds on commit to docs (only)
* docs_deploy2
* lower case waypoint file
* Lower case console.jpg
* Add duplicate index as fallback
* Get path from process
* fix upload
* Disable running workflows for changes in the actions
* Attempt update via github workflow
* Attempt workflow update
* A bit more deployment debugging
* MOdify yaml to use personal access token
* Lower case the support.md
* Fix up pattern
* Add UI design - ignored by github
* Fix up plugins name
* Fix up toolbar
* Fix up the Support path
* Fix up support link to go to the NEW target
* Only build this on commit
* Add docs stablev4 3 (#10894)
* docs_deploy1
* Disable platform builds on commit to docs (only)
* docs_deploy2
* lower case waypoint file
* Lower case console.jpg
* Add duplicate index as fallback
* Get path from process
* fix upload
* Disable running workflows for changes in the actions
* Attempt update via github workflow
* Attempt workflow update
* A bit more deployment debugging
* MOdify yaml to use personal access token
* Lower case the support.md
* Fix up pattern
* Add UI design - ignored by github
* Fix up plugins name
* Fix up toolbar
* Fix up the Support path
* Fix up support link to go to the NEW target
* Only build this on commit
* Remove unused files
Remove double call to make
Specify androiddeployqt location
Revert "Specify androiddeployqt location"
This reverts commit cc307cf32f0e9040aa8256d8b2799f8ff9168b9c.
Revert "Remove double call to make"
This reverts commit 3fee0e92fc537bee6586f674b8bf58463f0257da.
Remove PRE_TARGETDEPS
Fix target dependency to prevent make loop
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
davidsastresas
André Kjellstrup
Junwoo Hwang
Julien Olivain
Julian Oes
jnomikos
Christian Rauch
Hamish Willee
Don Gagne
Nick Exton
PX4BuildBot
James Mare