[Greg McKaskle]

I looked through the documentation, but couldn't find specifics. At least for the LV entry points the API is pretty forgiving and pretty intelligent. The underlying call to imaqColorThreshold takes in Range* datatypes for the three color specifications. A Range is two ints, which can encode 32 bit ints. I tested the LV entry points and they pin the ints into a reasonable range, so 256 is the same as 255. I'd expect the C functions to do the same. I don't have the signature for the RGBThreshold wrapper in WPILib, but as long as it uses ints and not int8s, there shouldn't be a problem, and even then, it would depend a bit on the ABI and implementation details.

Greg McKaskle