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.
* qgroundcontrol.pro: use gold linker if available (on linux)
Speeds up linking by ~4s on my machine.
* linux-fixup-rpaths.bash: use timestamp file to avoid unnecessary re-evaluation
Speeds up incremental builds, this step takes ~17s.
In case when you would like to bind some MAV commands
to some joystick's buttons, you can now create a json file
which will be parsed at runtime.
It is usefull when you need to send a custom command from the joystick.
But this command is not supported by the firmware, or not relevant to be included to QGC.
Example:
Create a file JoystickMavCommands.json and place it with a binary:
"commands": [
{
"id": 31010,
"name": "Enable Autonomy",
"param1": 1.0
}
]
After executing the QGC, you will be able to bind "Enable Autonomy" to a button,
by clicking to the button, MAV_CMD_USER_1 (31010) with param1 1.0 will be sent.
If there is no json file, nothing will happen.
The general goal is to tidy up the project folder and give better focus on other contents of the project.
As a first iteration, I would like to tidy up files, which are Windows related. Technically seen I'm pretty sure that we won't notice any differences, since some libraries and images have been moved and some config files cleaned up.
Signed-off-by: Thomas Karl Pietrowski <thopiekar@gmail.com>
* MockLink - Support REQUEST_MESSAGE:AUTOPILOT_VERSION, REQUEST_MESSAGE:PROTOCOL_VERSION
* Fix bugs in Vehicle::requestMessage
* Switch to all INT mission items
* Create unit tests to exercise Initial Connect state mache state failure conditions
Don Gagne
Beat Küng
davidsastresas
Nick Exton
Holden
honglang
Val Doroshchuk
Atanas Batinkov
Thomas Karl Pietrowski
Don Gagne
Lukas Bachschwell
Jenner Lochridge
jennerl
DonLakeFlyer
Patrick José Pereira
Dima Ponomarev
Aleksey Kontsevich