NI Motion: "Coordinate ID"... bug?

[Daklu]

I've been doing some programming with NI Motion and came across a VI that appears to have a minor bug.

Most of the VIs in the package use enums to input axes or vector spaces, but one vi appears to have forgotten to pick up the enum on his way out the door. Instead of the normal "Axis or Vector Space" input, Load Move Constraint.flx has an "Axis or Coordinate ID" input. That input has an I32 strict typedef associated with it, compared to a U16 with the normal enum input.

I've come up empty searching help for "Coordinate ID" so I assume it's a bug. I'm guess I could set the I32 to the value of the equivalent enum... haven't tried it yet though.

(A few of the camming VIs use "Axis ID" in a similar manner.)