How to use COMMAND_INT

From what I understand COMMAND_INT is in Mission Planner's Mavlink message definations [here](https://github.com/diydrones/MissionPlanner/blob/fea7ba06b4c1f6e6d1def8481153ac4941d1c321/ExtLibs/Mavlink/generator/message_definitions/common.xml#L2326) and is said to be supported in autopilot [here](https://github.com/diydrones/MissionPlanner/blob/fea7ba06b4c1f6e6d1def8481153ac4941d1c321/ExtLibs/Mavlink/generator/message_definitions/common.xml#L2326).
Mission Planner uses [COMMAND_LONG](https://github.com/diydrones/MissionPlanner/blob/fea7ba06b4c1f6e6d1def8481153ac4941d1c321/ExtLibs/Mavlink/generator/message_definitions/common.xml#L2342) by default.
It was said in a Mavlink issue [here](https://github.com/mavlink/mavlink/issues/426#issuecomment-132340142) that COMMAND_LONG and COMMAND_INT were interchangable.

Is there any way to use COMMAND_INT in Mission Planner?

Start with the linked common.xml definitions for COMMAND_INT and COMMAND_LONG, then trace Mission Planner's existing COMMAND_LONG handling to find the relevant entry point. Done means establishing whether Mission Planner exposes COMMAND_INT and documenting the required usage or identifying the implementation area needed to support it.

Written by the indexing model from the issue text.