Skip to content
  1. Nov 25, 2014
    • Don Gagne's avatar
      File renames · 68a59a78
      Don Gagne authored
      68a59a78
    • Don Gagne's avatar
      Use new QGCMessageBox apis · db7b86fb
      Don Gagne authored
      Subclass of QMessageBox which re-implements the static public
      functions. There are two reasons for this:
      1) The QMessageBox implementation on OSX does now show the title
      string. This leads to message boxes which don't make much sense. So on
      OSX we set title to text and text to informative text.
      2) If parent is NULL, we set parent to MainWindow::instance. This
      prevents message boxes which can go behind MainWindow
      db7b86fb
  2. Nov 24, 2014
    • 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
  3. Nov 14, 2014
  4. Oct 23, 2014
  5. Aug 05, 2014
  6. Jul 31, 2014
  7. Jul 25, 2014
  8. Jul 23, 2014
    • Bryant's avatar
      Removing all SLUGS autopilot-specific code. · 9d8d4c5b
      Bryant authored
      SLUGS has maintained their patches out-of-tree for a long while now.
      These will eventually get merged back in, but it'll be easier to evaluate them as fresh commits instead of modifications to this old & dead code, so we'll delete this for now.
      9d8d4c5b
  9. Jul 20, 2014
  10. Jun 27, 2014
  11. Jun 15, 2014
  12. May 24, 2014
  13. May 19, 2014
  14. May 18, 2014
  15. May 15, 2014
  16. May 07, 2014
  17. May 06, 2014
    • 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
  18. Feb 14, 2014
  19. Nov 05, 2013
  20. Sep 26, 2013
  21. Aug 26, 2013
  22. Jul 16, 2013
  23. Jun 13, 2013
  24. Jun 10, 2013
  25. Jun 09, 2013
  26. May 14, 2013
  27. Apr 25, 2013
  28. Apr 17, 2013
  29. Apr 16, 2013
  30. Apr 11, 2013
    • Christopher Hrabia's avatar
      Revert last change on new logfile structure and added nulling of buffer. · 50c36bb5
      Christopher Hrabia authored
      The reason for this is, because the last change in the file structure is buggy, it was only written the message length of the buffer to the file and missed to add the length for the timestamp.
      For fixing this problem it would be possible to insert something like
      
      len += sizeof(quint64);
      
      after:
      
      int len = mavlink_msg_to_send_buffer(buf+sizeof(quint64), &message);
      
      But I think a consistent file structure has more adavatages for a logfile over a more compressed structure.
      E.g. it would be necessary to go through all packages to proceed a jump during a replay.
      Additional the LogPlayer was not updated during the last 7 month since the logfile structure was changed (even it was buggy)...
      
      If filesize is really a problem I would recommend to change the logfile handling in a way of writting a temporary consistend
      logfile and compress it afterwards (QCompress) like done by many programs
      50c36bb5
  31. Sep 16, 2012
  32. Sep 13, 2012
  33. Sep 07, 2012
Loading