Michael du Breuil 7a18d59099 GCS_MAVLink: On mission_set_current report the requested item if the set was a success ... The problem with reporting the mission index, is that the mission index will be walked forward until its referring to a nav target, which means that if a DO_ command was requested, the requesting mavlink device had no way to validate the command was accepted, it would have to make a infrence from it's copy of the mission		2016-09-06 08:55:04 +10:00
..
examples/routing	GCS_MAVLink: fixed typo	2016-07-01 15:35:49 +10:00
.gitignore	Updated MAVLink to 1.0.6 release.	2012-04-19 15:46:29 -04:00
GCS_Common.cpp	GCS_MAVLink: On mission_set_current report the requested item if the set was a success	2016-09-06 08:55:04 +10:00
GCS_Logs.cpp	GCS_MAVLink: coverity scan - computed value overwritten without use for SITL	2016-07-05 13:32:29 -07:00
GCS_MAVLink.cpp	GCS_MAVLink: handle difference between SERIALn_PROTOCOL=1 and 2	2016-05-21 15:25:17 +10:00
GCS_MAVLink.h	GCS_MAVLink: always build with MAVLink2 headers	2016-05-21 15:25:16 +10:00
GCS_serial_control.cpp	GCS_MAVLink: adjust for min_length mavlink2 API change	2016-05-21 15:25:15 +10:00
GCS_Signing.cpp	GCS_MAVLink: check the signing key magic on load	2016-09-04 19:28:48 +10:00
GCS.h	GCS_MAVLink: added handle_preflight_reboot()	2016-08-16 12:53:33 +10:00
MAVLink_routing.cpp	GCS_MAVLink: do not auto-forward ADSB_VEHICLE packets	2016-06-19 11:24:29 -07:00
MAVLink_routing.h	Revert "GCS_MAVLink: coverity scan - variables not initialized in constructor"	2016-07-11 22:01:50 -07:00