ARCADE-UAV/mavlink — comment on commit e68429a2d98f8e9cae064f9818a5d3afe423829e
File:  line 0
By Susurrus:

I do agree with that, even as silly as it is to have redundant data types, that is probably wise. So what should really happen then is that MAV_VAR should stay in the MAVLink implementation and QGC should be updated to use MAV_VAR instead of MAVLINK_TYPE_*.

A nice way to prevent things from breaking on the autopilot side is to replicate the MAVLINK_TYPE_* as it is now for the MAV_VAR enum. Not really the best way I don't think, but it's an option, as I don't see the point of MAVLINK_TYPE_CHAR (I also think that the C-specific FLOAT and DOUBLE should be renamed to the generic REAL32 and REAL64).