1. 01 Jul, 2016 1 commit
  2. 04 Feb, 2016 1 commit
  3. 20 Jan, 2016 1 commit
  4. 25 Dec, 2015 1 commit
  5. 24 Dec, 2015 1 commit
  6. 23 Nov, 2015 1 commit
    • Don Gagne's avatar
      Auto connect support · b9cb57ec
      Don Gagne authored
      - Pervasive change to automatically connect to known board types
      - Lots of additional changes along with this:
      - More exposure of objects/properties to Qml
      - Much restructuring in LinkManager and LinkManager clients
      b9cb57ec
  7. 19 Nov, 2015 1 commit
    • Don Gagne's avatar
      Auto connect support · 18dc3d04
      Don Gagne authored
      - Pervasive change to automatically connect to known board types
      - Lots of additional changes along with this:
      - More exposure of objects/properties to Qml
      - Much restructuring in LinkManager and LinkManager clients
      18dc3d04
  8. 18 Nov, 2015 1 commit
    • Don Gagne's avatar
      Auto connect support · aaed8c2d
      Don Gagne authored
      - Pervasive change to automatically connect to known board types
      - Lots of additional changes along with this:
      - More exposure of objects/properties to Qml
      - Much restructuring in LinkManager and LinkManager clients
      aaed8c2d
  9. 30 Oct, 2015 1 commit
  10. 26 Jul, 2015 1 commit
  11. 25 Jul, 2015 1 commit
  12. 31 May, 2015 1 commit
  13. 29 Apr, 2015 1 commit
  14. 02 Apr, 2015 1 commit
    • Don Gagne's avatar
      Resource restructuring · d5146cd2
      Don Gagne authored
      - All resources are either under src or under resources dirs
      - Removed files top level directory
      - Move flightgear files to top level dir
      d5146cd2
  15. 28 Mar, 2015 1 commit
    • Don Gagne's avatar
      Remove link ids and add link mavlink channel · 4f5984b3
      Don Gagne authored
      Link ids were being used interchangeably with the mavlink channel for
      the link. Link ids handed out as a numerically increasing integer. Once
      the counter went past MAVLINK_COMM_NUM_BUFFERS all hell would break
      loose and cause memory corruption.
      4f5984b3
  16. 22 Mar, 2015 1 commit
  17. 04 Feb, 2015 1 commit
  18. 03 Feb, 2015 1 commit
  19. 26 Dec, 2014 1 commit
  20. 12 Dec, 2014 1 commit
    • Don Gagne's avatar
      Move UAS and MAVLinkProtocol back to main thread · fc493d75
      Don Gagne authored
      Plus a large number of other changes to allow for orderly shutdown of
      objects without crashes or asserts. This is need for unit tests to
      create/delete global state around every test.
      fc493d75
  21. 27 Nov, 2014 2 commits
  22. 25 Nov, 2014 2 commits
  23. 24 Nov, 2014 2 commits
    • Don Gagne's avatar
      Use new QGCFileDialog api · 10a00eb0
      Don Gagne authored
      Using QFileDialog directly on OS X can hang intermittently due to Qt
      bug.
      10a00eb0
    • Don Gagne's avatar
      New mavlink logging support · 6d7fb36a
      Don Gagne authored
      - Logging now always on to temp file
      - User prompted to save temp file after disconnect
      - Orphaned temp logs checked for on boot
      - Logs saved to new save file location
      - Log file starts/stops with first and last connnection
      6d7fb36a
  24. 27 Jun, 2014 1 commit
  25. 10 Jun, 2014 1 commit
    • Bryant Mairs's avatar
      Fix for #647. · 4b07086f
      Bryant Mairs authored
      In the logplayer, the data stream is read ahead for messages, which is used to determine the size of the output bytearrays. Previously, this wasn't done correctly resulting in non-ideal behavior. Now, the next message is scanned properly, so the only bytearrays that are emitted from QGCMAVLinkLogPlayer are MAVLink messages in their entirety. This also has the benefit of skipping invalid/corrupted messages in the log that's being played back.
      4b07086f
  26. 25 May, 2014 1 commit
  27. 06 May, 2014 1 commit
    • Bryant Mairs's avatar
      QGC data logging now records small MAVLink messages. · 321f21f2
      Bryant Mairs authored
      Previously MAVLink data streams recorded by QGC would use a fixed block size of the maximum MAVLink message length and fill in only the bytes written by the message. This wasted space, make manual parsing difficult, and broke compatibility with scripts provided in the MAVLink project (issue #174).
      
      This patch alters logging to output only a packed data stream (64-bit big endian unix timestamp in microseconds since epoch + MAVLink message) instead of the unpacked data stream previously output. Additionally the previous logging code used the system endianness for packing in the timestamp, this has now been switched to always be big endian regardless of platform. All the documentation specifies big endian, so the code now follows the docs here.
      
      Additionally data playback has been modified to playback both the new packed data streams as well as the old data streams, even those with improper endianness for their timestamps.
      
      Finally, a variety of bugs have been fixed, along with some additional features and user experience changes, hopefully for the better. All existing functionality has been preserved as well.
      321f21f2
  28. 31 May, 2013 1 commit
  29. 25 May, 2013 1 commit
  30. 05 May, 2013 1 commit
  31. 02 May, 2013 1 commit
  32. 29 Apr, 2013 1 commit
  33. 23 Apr, 2013 1 commit
  34. 18 Apr, 2013 1 commit
  35. 17 Apr, 2013 1 commit
  36. 08 Aug, 2012 1 commit
  37. 25 Jul, 2012 1 commit