- 20 Jul, 2018 1 commit
-
-
Gus Grubba authored
-
- 14 Jul, 2018 1 commit
-
-
Beat Küng authored
-
- 26 Jun, 2018 1 commit
-
-
acfloria authored
-
- 15 Jun, 2018 1 commit
-
-
Patrick José Pereira authored
Signed-off-by: Patrick José Pereira <patrickelectric@gmail.com>
-
- 05 Jun, 2018 1 commit
-
-
DonLakeFlyer authored
-
- 01 Jun, 2018 1 commit
-
-
DonLakeFlyer authored
-
- 16 May, 2018 1 commit
-
-
acfloria authored
Add the HeartbeatTimer class to track a single heartbeat for a single link. For every new received heartbeat an instance of the class is created. Every instance emits a signal if it timed out or the timer is restarted. Each vehicle then decides based on all different signals which link is the priority link.
-
- 01 May, 2018 1 commit
-
-
DonLakeFlyer authored
-
- 30 Apr, 2018 1 commit
-
-
DonLakeFlyer authored
-
- 05 Apr, 2018 1 commit
-
-
DonLakeFlyer authored
-
- 23 Mar, 2018 1 commit
-
-
DonLakeFlyer authored
-
- 22 Mar, 2018 1 commit
-
-
Gus Grubba authored
The build system will look for src/Airmap/Airmap_api_key.h If it find is, it will used the provided API key and client ID for Airmap. That file should provide two strings: static const char* kAirmapAPIKey = "key data"; static const char* kAirmapClientID = "id data"; Local builds, without these will have no Airmap support by default (users can always enter their own within the Airmap settings panel).
-
- 16 Mar, 2018 1 commit
-
-
DonLakeFlyer authored
-
- 07 Mar, 2018 3 commits
-
-
Gus Grubba authored
It builds clean but the resources still get messed up (loads true qml files instead of dummy ones, and it crashes...)
-
mantelt authored
-
mantelt authored
-
- 18 Feb, 2018 1 commit
-
-
Gus Grubba authored
Make all argument to AirMap queries based on what the screen shows (bounding rectangle and/or radius), respecting the limits imposed by AirMap.
-
- 16 Feb, 2018 2 commits
-
-
Gus Grubba authored
Moved flight planning away from "Flight Management" to its own class. Planning does not need a connected vehicle.
-
Gus Grubba authored
AirspaceManager is now exposed by QGroundControlQmlGlobal instead of Vehicle (available all the time)
-
- 05 Feb, 2018 2 commits
-
-
DonLakeFlyer authored
-
Daniel Agar authored
-
- 04 Feb, 2018 1 commit
-
-
DonLakeFlyer authored
-
- 30 Jan, 2018 1 commit
-
-
DonLakeFlyer authored
-
- 27 Jan, 2018 8 commits
-
-
Gus Grubba authored
-
Gus Grubba authored
-
Gus Grubba authored
-
Gus Grubba authored
-
Gus Grubba authored
-
Gus Grubba authored
Break apart string of classes into their own files as all in one file became unwieldy Expose Airspace data in a QML ready format Split global Airspace from AirMap (Only now I figured out the reason for the pure virtual root classes) Refactored a bunch of things to make it consistent and/or obvious
-
Gus Grubba authored
-
Gus Grubba authored
Move all airmap related stuff to its own directory
-
- 31 Dec, 2017 1 commit
-
-
DonLakeFlyer authored
-
- 19 Dec, 2017 1 commit
-
-
Beat Küng authored
which is now a shared library
-
- 13 Dec, 2017 1 commit
-
-
DonLakeFlyer authored
-
- 12 Dec, 2017 1 commit
-
-
DonLakeFlyer authored
-
- 04 Dec, 2017 1 commit
-
-
Gus Grubba authored
-
- 29 Nov, 2017 4 commits
-
-
Beat Küng authored
-
Beat Küng authored
You need to adjust the 'AIRMAPD_PATH = path_to_airmapd' in qgroundcontrol.pro to make it compile. And sorry for the huge commit :/
-
Beat Küng authored
- add multi-vehicle support: each vehicle has now a per-vehicle AirMap object that takes care of flight creation, traffic & telemetry - add a base class API layer so that the interface between QGC and the AirMap implementation is clear, and easier to change - removes polygon upload to vehicle (needs a better solution)
-
Gus Grubba authored
Added AirMap settings (SettingsGroup) Added AirMap settings block to General Settings Create macros to deal with the tedious repetitions within SettingsGroup Removed old, hacked in setting for AirMapKey Remove a few of the tons of build warnings
-