TWAIN Working Group

Newsletter Signup
Donate
Help keep TWAIN free
  • About TWAIN
    • What’s New?
    • News
    • Events
    • Membership
    • Consider a Donation
    • Contact Us
  • Why TWAIN?
  • Developers
    • Driver Developer
    • Application Developer
    • TWAIN Features
    • Specification & Tools
    • Self Certification Process
  • Support Forums
  • Scanner End-User
  • Find Certified Drivers
    • Facebook
    • LinkedIn
    • Vimeo

undefined condition codes

Forums › TWAIN Classic › undefined condition codes

  • This topic has 2 replies, 2 voices, and was last updated 13 years, 10 months ago by gabe.
Viewing 3 posts - 1 through 3 (of 3 total)
  • Author
    Posts
  • June 9, 2007 at 1:59 pm #22157 Reply
    gabe
    Participant
    • Topics - 9
    • Replies - 583
    • Total Posts - 592

    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?
    .

    June 12, 2007 at 9:25 pm #23843 Reply
    MarkM
    Participant
    • Topics - 1
    • Replies - 135
    • Total Posts - 136

    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

    June 12, 2007 at 11:44 pm #23844 Reply
    gabe
    Participant
    • Topics - 9
    • Replies - 583
    • Total Posts - 592

    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,

    .

  • Author
    Posts
Viewing 3 posts - 1 through 3 (of 3 total)
Reply To: Reply #23843 in undefined condition codes
Your information:




Quick Links

Service Providers
TWAIN Support Forums
Membership
Contact Us
Privacy Policy

Newsletter Signup

TWAIN Working Group Family

TWAIN Working Group
TWAIN Direct®
TWAIN Resources
TWAIN Certified Drivers
PDF/raster

  • Facebook
  • GitHub
  • LinkedIn
  • Vimeo

Recent Topics

  • TWAIN for dental imaging integration
  • PDF/R For who and where?
  • Making searchable PDF with PDF/R
  • Backward compatibility with PDF/A and traditional PDF
  • could not open the twain source. Make sure there is a valid source for your sca
  • Quarterly Newsletter
  • TWAIN Working Group Membership
  • Logo Usage
  • TWAIN License
  • Contact Us
Privacy Policy • Privacy Tools • Copyright © 2021 TWAIN Working Group • by iHwy, LLC • Log in

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.