Forum Replies Created
- AuthorPosts
Spike,
Agreed. If not already in the errata / it will be added.
TWAIN 2.0 applications are expected to load the new DSM.
Jon Harju
Syed,
Sample code and the TWAIN specification are available for download at http://twain.org
Jon Harju
@scanlabs wrote:
We are looking to outsource the development of Apple OSX Tiger 10.4 Twain drivers for high-speed document scanners.
Have you found anyone yet? We would be interested in quoting such a job.
@sparge wrote:
Is ActiveX anything to do with DirectX? There is a tool that can interrogate the state of health of DirectX on a PC; I wonder if there is anything similar for ActiveX? Sounds like a good line of Google enquiry.
ActiveX is just a way of integrating 3rd party software into the user interface of any application. Depending on how the TWAIN driver was put together, it may or may not use any ActiveX controls.
Since these are typically 3rd party components, it is possible that some other software upgrade can cause problems.
Unfortunately there is no easy way for you to know what may or may not have happened here, except try to think of what kinds of changes you have made to your system since it was last working properly. Any un-related updates you applied or software you have installed.
In the end such a list might offer some clues, though ultimately the scanner manufacturer is the only one that can confirm or deny any potential conflicts for you.
@sparge wrote:
“eradicate any driver specific presets from your computer”
Not sure what you mean by this. Can you elaborate a wee bit please?
I was referring to any settings files or registry entries that are not typically touched by the un-install programs. Usually session settings are stored and restored from either a configuration file or a registry section and they often survive the process of re-installing. If unexpected values are poorly handled by the driver in question, then it might be helpful to manually delete anything you find left over after an uninstall.
I have no specifics for you, since the implementation of this is completely up to the manufacturer.
Jon Harju
@nader wrote:
HI everyone.
I’ve got a canon dr-2580C and a dr-2080c both use twain driver as well as isis.
I’ve got a problem with auto-detect function in both model. This function only works with programs that came with these scanners but not with adobe acrobat, photoshop, microsoft imaging, ….. Why does the function auto-detect doesn’t exist when I use other programs ??Thanks !
That would be a question for Canon. My memory of the DR-2080C is that the autodetect feature is not exposed via the standard TWAIN mechanisms for doing this so. I think there are some proprietary custom capabilities related to this, but the application has to have specific knowledge about these settings to turn them on. Something your basic off the shelf application does not know.
Jon Harju
@sparge wrote:
So it appears that there is a problem specifically to do with being in state 5. I’d really love to hear some informed guesswork on this one!
My guess would be that the DS GUI uses some ActiveX component that is no longer working due to some recent update to your computer. Or there are some settings files or registry settings that have been corrupted. You might be able to fix it if you re-install the driver or if you can find a way to eradicate any driver specfic presets from your computer.
Jon Harju
@Thierry wrote:
Hi,
I’m facing a new problem (unexpected), using a i620 kodak scanner (directly trough FireWire) with my laptop. The problem is that I can tranfert only one image, instead of 3 or 4 depending of the number of sheets actually in the feeder.
The pending image count is not updated correctly, and always set to 0, but the scanner continues to scan pages anyway.
The only way to solve this problem is to introduce an ugly Sleep(500), between TWRC_XFERDONE and before sending MSG_ENDXFER. Doing that the pending image count is 65535 which is normal for me.
Is this normal 🙄 ? Actually that’s the only scanner I’ve seen doing this.
No, this is not normal. You need to contact Kodak for more information on that one.
Best Regards,
Jon Harju@spike wrote:
Can anybody share any experience with doing compressed memory transfers? Quirks, pitfalls, etc.? The TWAIN 1.9 spec is pretty terse on this subject.
Can anybody suggest an under 1000$US scanner that supports compressed memory transfers, for testing and development?
How do you tell which values of ICAP_COMPRESSION apply to files, and which to memory transfers? I imagine that you set ICAP_XFERMECH to TWSX_MEMORY, and then query ICAP_COMPRESSION. But does that really work in practice?
No real pitfalls, other than the fact that G4 is raw G4 data – ImageInfo is required to make any real use of the data after collecting it all, the only field of th TW_IMAGEMEMXFER structure that you can use is the BytesWritten – all others should be (-1)
JPEG is a different animal, the entire JPEG file is transferred in memory and can be written directly to a file with extension .jpg to be immediately useful.
Just loop until you get a TWRC_XFERDONE – there is no real way to figure out how much data you can expect or how many calls you need to make to ImageMemXfer, as each compressed image size depends on content.
I can’t direct you to a scanner within that price range, I can tell you that most scanners I have worked with that are sub 30 pages per minute tend not to support compression.
Compression is usually associated with speed and volume.
Jon Harju
Thilak
If you are referring to the TWAIN driver settings dialog, then you need to look at the TWAIN Specification under MSG_ENABLEDS / you need to set the ShowUI member of the structure passed in to false to suppress that dialog. Another capability to look at is the CAP_INDICATORS.
How successful this is really depends on the driver you are using and what UI you are trying to get rid of.
Jon Harju
The version of the TWAIN Data Source Manager does not imply any limitation on the features you can use with it. The Data Source Manager is a pass through.
The limiting factor is the TWAIN driver – assuming the Fujitu TWAIN Driver supports those features you need not worry about the version of the DSM files located in the Windows Directory.
Best Regards,
Jon HarjuCheck out the resources section of http://www.TWAIN.org for a list of companies that provide toolkits and development services.
What you are looking for is an ActiveX control that hides the TWAIN details for you.
A google search for TWAIN ActiveX should also produce what you are looking for.
Best Regards,
Jon HarjuHello,
It’s not clear what you mean by buttons not working, this could be a variety of things. A few of them are event loop related as you have surmised…
Remember to forward all messages using DAT_EVENT/MSG_PROCESSEVENT and inspect the return code. If the return code is TWRC_DSEVENT then you have to inspect the TWMessage component of the structure – if this is MSG_XFERREADY or MSG_CLOSEDSREQ then you are expected to do something. It is possible that TWMessage will not be either of these in which case you are just supposed to ignore it and continue on to the next message in the queue.
If the return code is TWRC_NOTDSEVENT then you are expected to allow windows to process the message normally with TranslateMessage, DispatchMessage calls.
Remember – if you recieve TWRC_DSEVENT – you are not to dispatch the message to TranslateMessage, DispatchMessage at all – this will cause all kids of strange GUI behavior if you do.
Best Regards,
Jon HarjuHello Matt,
What exactly is it that you are having problems with? The sample code from the TWAIN website achieves multipage scanning… are you trying to do something complicated?
If you are already scanning single pages without trouble, then simply add a loop that inspects the value of PendingXfers.Count after each call to DAT_PENDINGXFERS/MSG_ENDXFER call.
ie:
do
{
GetImageInfo();
GetMemoryTransfer();
}while(PendingXfers.Count != 0);Best Regards,
Jon Harju- AuthorPosts