Home › Forums › TWAIN Classic › undefined condition codes
- This topic has 2 replies, 2 voices, and was last updated 16 years, 10 months ago by gabe.
- AuthorPosts
looking thru the twain header from twain.org and at the twain2d twain spec something occurs to me. Where are condition codes 7 & 8? And while I’m comparing the spec to the header, the header defines 2 CCs that I don’t see in the spec: FileWriteError(22) and CheckDeviceOnline(23). The CCs missing from the spec don’t bother me (at least not nearly as much as other errors in the spec), but the missing CCs 7 and 8 are somewhat troubling as I’m getting CC = 8 from a Kodak scanning when running thru the standard ExtImageInfo values.
Any takers?
.Hi Gabe…
I’m in a hunt now to see if I can find out what 7 and 8 are, although, as I understand it, we’ve found them missing going all the way back to 1.7, so I might have to delve into the really old stuff to get an answer. I think it’s moot though becase…
As for TWEI_ tossing an 8 from a Kodak scanner: welcome to TWRC_INFONOTSUPPORTED. This is one of those things that gives me heartburn. Apparently, the intention was to have something called RetCode in the TW_INFO field (which was added in 1.7). You can still see this field mentioned in the TWAIN Specification. Well, somewhere along the way that field was changed to CondCode inside of TWAIN.H, but TWRC_INFONOTSUPPORTED didn’t change to TWCC_INFONOTSUPPORTED, and the Spec didn’t get fixed.
Augh…
Hope that makes it more clear…
— Mark
That does help, tons. If you get further in the search please let me know.
… it makes me wonder how many vendors return an rc and how many a cc but I can adjust my twei_ code somewhat for cases where the cc returned isn’t defined. For the most part this isn’t going to affect much more than some logging code that I have in place,
thank you,
.
- AuthorPosts