mavlink/mavlink — pull request #293 by mpaperno (2014-12-02 11:34:10+00:00)
Title: mavparse.py: append ENUM_END only after merging/sorting

With custom definition files, this way we can add new enum values to the end of existing (common) enums and the ENUM_END is calculated and placed correctly.

Eg. I wanted to do something like this in our autoquad.xml file:

Motor/ESC telemetry data.

The way it is now, the MAV_DATA_STREAM_ENUM_END value would = 13, and I would get a duplicate value error unless I used 14 or higher for my new entry... but then the ENUM_END was wrong, defeating the purpose.

Thanks,
-Max