1. 07 Oct, 2014 1 commit
  2. 02 Sep, 2014 1 commit
  3. 23 Aug, 2014 2 commits
  4. 21 Aug, 2014 1 commit
  5. 22 May, 2014 4 commits
  6. 19 May, 2014 1 commit
  7. 07 May, 2014 1 commit
  8. 17 Feb, 2014 2 commits
  9. 13 Feb, 2014 2 commits
  10. 13 Aug, 2013 1 commit
  11. 08 Aug, 2013 1 commit
  12. 28 May, 2013 1 commit
  13. 25 May, 2013 3 commits
  14. 01 May, 2013 1 commit
  15. 06 Sep, 2012 1 commit
  16. 07 Aug, 2012 1 commit
  17. 13 Jul, 2012 1 commit
  18. 28 Jun, 2012 3 commits
  19. 05 Jun, 2012 1 commit
    • Andrew Tridgell's avatar
      don't reject waypoints based on component ID · 4fa4be0b
      Andrew Tridgell authored
      as long as the waypoint comes from the right systemID there is no
      point rejecting it based on component ID. 
      
      The current_partner_compid is also completely wrong in the code, so
      checking it makes no sense anyway
      4fa4be0b
  20. 30 May, 2012 1 commit
  21. 15 Feb, 2012 1 commit
  22. 14 Feb, 2012 1 commit
  23. 08 Feb, 2012 2 commits
  24. 13 Jan, 2012 1 commit
    • pixhawk's avatar
      Some more bugfixes and improvements for the Mission Plan widget. The... · aa5d5043
      pixhawk authored
      Some more bugfixes and improvements for the Mission Plan widget. The "current"-checkbox in "Onboard"-waypoints can no longer be changed by clicking directly, but it is handled internally by QGC. Now there should be one and only one checked checkbox, which shows the last KNOWN "current" waypoint on MAV. The white border around an unchecked checkbox means, that the user is requesting the change of current waypoint, but QGC has not received MISSION_CURRENT message as a confirmation yet. Also,if there is no response from UAV after pushing "Read" or "Refresh", the "Onboard" list will be deleted to indicate, that there is no information available.
      aa5d5043
  25. 11 Jan, 2012 1 commit
  26. 09 Jan, 2012 2 commits
  27. 22 Nov, 2011 1 commit
  28. 06 Nov, 2011 1 commit