These Custom Actions are defined in a JSON file, and define MAVLink
messages to send to the current active vehicle. These Custom Actions
will be added to the Fly View.
Github workflow image ubuntu-20.04 version 20230313.1 have added Android
SDK Platform android-33-ext5. Something, possible the gradle version
bundled with qt does not parse this correctly, and sets
androidCompileSdkVersion in android-build/gradle.properties to "ext5"
instead of expected "33". This commit is a quick fix to the problem, so
the build will revert to android-33 which was used before 20230109.1.
This fix was previously added for android-33-ext4 in image 20230109.1 in
commit 6f636e7891.
My experience is that I change heading to absolute direction, rather
than relative (because relative will accumulate any heading error on
incomplete yaw, especially if the command is executed while turning.)
The absolute heading is the most used/typical way of using this mission
item. This change does not affect missions that are already created,
only the default selection while creating a mission.
The default yaw rate is also very slow (unchanged) meaning that any
relative yaw command will result in an unknown result, unlress performed
long since last one relative.
Final reason: Scanning missions consists of with many waypoints are
always at an absolute heading. While "make a panoramic turn" with
relative amont of degrees, are usually single-command. So it is better
to default to a setting used for missions with many such commands.
Co-authored-by: forced_to_this_mess <eudhe@deed.no>
_providersTable["Google Labels"] has constructed with GoogleTerrainMapProvider class as wrongly. It have to construct with GoogleLabelsMapProvider class.
Releasing a hat button did not lead to _executeButtonAction being called with BUTTON_UP. This adds the hat buttons to lastBbuttonValues, such that the button-up transitions for hat buttons are recorded.
* Fix for #10574
* This will affect everywhere which uses the QGCFlickable base control. This is the majority of everywhere but may be mission in some places. If fast scrolling is seen in specific spot it needs to changes to use QGCFlickable instead of Flickable.
When metadata was loaded from JSON and decimal places weren't
specified it was set to 0 when it should have been set to
kUknownDecimalPlaces (which will in turn default to 3).
---------
Co-authored-by: Don Gagne <dongagne@outlook.com>
The whole point of COMMAND_INTs is that they have better resolution for
coordinates leveraging int32 for degrees*10^7. This resolution is lost
if we use float while handling the data instead of double.
Signed-off-by: Julian Oes <julian@oes.ch>
Github workflow image ubuntu-20.04 version 20230109.1 have added Android
SDK Platform android-33-ext4. Something, possible the gradle version
bundled with qt does not parse this correctly, and sets
androidCompileSdkVersion in android-build/gradle.properties to "ext4"
instead of expected "33". This commit is a quick fix to the problem, so
the build will revert to android-33 wich was used before 20230109.1.
Philipp Borgers
PX4BuildBot
davidsastresas
Nick Exton
Knut Hjorth
André Kjellstrup
Tevhit Karsli
Kjersti Brynestad
Mathieu Mirmont
WTPENGUIN
Don Gagne
Patrick José Pereira
Christian Rauch
FARHANG
AndKe
Julian Oes
Robbie Drage
Don Gagne
Don Gagne
Vincent Poon