This enables two UI features when connected to an ArduPilot vehicle:
1. click the map in the Fly View and send an "ROI at Location" command; and
2. add an ROI as part of a Mission Plan.
Note that there is no way to determine if an ArduPilot build will accept
these commands. The commands will be accepted if the current connected
ArduPilot vehicle has both:
1. the Mount driver included (i.e. compiled with HAL_MOUNT_ENABLED); and
2. a Mount driver enabled (via the MNTn_TYPE parameter)
If ROIs are not supported, the ArduPilot vehicle will respond with a
MAV_RESULT_UNSUPPORTED command ack message.
Addresses #10640.
When there are multiple vehicles, and you select a vehicle, the joystick should switch over to the newly active vehicle, and only the active vehicle (so that joystick inputs are not sent to a vehicle you do not intend to control).
To resolve this, we connect Vehicle to the activeVehicleAvailableChanged and activeVehicleChanged signals produced by the MultiVehicleManager. ALL vehicles disable joystick when activeVehicleAvailableChanged(false), because this signals when there is no longer an active vehicle available. When activeVehicleChanged is signalled, ONLY the currently active vehicle enables joystick.
See issue #10544.
we were using the geopositioninfo.isValid() in order to discard
GPS and send lat/long/alt 0, but this function returns true
even if latest GPS refresh was long time ago, so now instead
we are using _gcsGPSGood, which takes into account the 5 seconds
timeout as well
In runtime, QGC needs:
- `vcruntime140.dll`
- `vcruntime140_1.dll`
- `msvcp140.dll`
- `msvcp140_1.dll`
The update is necessary because `vcruntime140_1.dll` is only
shipped after MSVC Redistributables version 17
We use github actions now and I remove the travis configuration file and
change the Vagrantfile that uses the travis file for configuration. I
remove build_ios script as well as it is nowhere in use and seems to be
part of the travis CI setup.
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>
Philipp Borgers
Patrick José Pereira
Christian Rauch
Nick Exton
Sergii Lisovenko
Christopher Vo
PX4BuildBot
Don Gagne
Don Gagne
davidsastresas
Beat Küng
João Antônio Cardoso
Knut Hjorth
André Kjellstrup
Tevhit Karsli
Kjersti Brynestad
Mathieu Mirmont
WTPENGUIN