Kodak Alaris Directory
Readme File
11-November-2013
The contents of this directory provide information about the custom features of the Kodak Alaris Inc. TWAIN driver.
Some hints for new application writers. The information here technically belongs in the FAQ, but we’re pulling it out to help jumpstart the development process for someone who is new to the Kodak Alaris Inc. Document Scanners, TWAIN or both.
A list of links pointing to Kodak Alaris Inc. and TWAIN driver support resources on the net.
A list of hints, help and Frequently Asked Questions concerning the Kodak Alaris Inc. TWAIN driver; integrators are strongly encouraged to look through this file when looking for information about how the driver works, how to integrate it, and some of the configuration tweaks and tricks that can be applied to help it work better in specific situations.
This is the C/C++ header file containing (and describing) all the custom TWAIN capabilities and operations supported by the driver. For more detail see TWAIN_Features.htm.
This describes the logging system for the Kodak Alaris Inc. TWAIN driver, though it also discusses a couple other diagnostic tools. This is probably the most important document to read if you are attempting to diagnose a problem using the driver. Note that it can be used to analyze the behavior of the application and the scanner too.
The Kodak Alaris Inc. TWAIN driver supports a simulation mode that allows integrators to test scanner models without a physical scanner. This document provides information on how to use the simulator.
This document is a bit of a mix between the current Kodak Alaris Inc. >DualStream functionality and a proposed Single Document Multiple Images proposal for the TWAIN Working Group.
Applications maximize their flexibility when they collect the meta-data associated with each image captured by the scanner. For simple applications DAT_IMAGEINFO is often enough information. More complex applications will want to use DAT_EXTIMAGEINFO. This document goes into some detail about how best to use the call, and what information it offers per image.
There’s a bit of source code in here to help uses who need to negotiate the rear cameras separately from the front cameras (this most often occurs when trying to set up simultaneous bitonal/color or bitonal/grayscale scanning using the custom CAP_CAMERAENABLE capability).
This document describes how all TWAIN and custom capabilities work for each scanner.
TWAIN_ProgrammaticPrinting.htm
This document describes how to programmatically drive the scanner printing functionality through the TWAIN interface, (as opposed to doing it through the driver GUI).
TWAIN_ScannerIdentification.htm
In an ideal world an application should never have to know the exact model number (save maybe to show the value to a user). This is our concession to reality.
TWAIN_Internationalization.htm
This section details the various ways that an application or user can select the language used by the driver.