[Greg McKaskle]

I completely agree. It is confusing and possibly brittle to use a number that won't fit into an int8, but as long as the RGBThreshold wrapper doesn't cause it to be cast, the underlying IMAQ functions appear not to treat 256 as 0, but instead treat 256 as 255. In other words, they pin the input number into range rather than cast it.

Again, I'm basing that on the behavior of the LV entry points, and the C version could be different.

Also, the IMAQ analysis functions also support int16 monochrome, float monochrome, and even RGB64 images, so the pinning is useful for those cases as well.

Greg McKaskle