@fct wrote:
I’m talking about the already-compiled TWAIN data source application linked from the front page in twain.org.
Okay, it will probably do a lot to orient me in the twain spec to run the testbed first,…I have to keep some idea of where I am at.
@fct wrote:
You’re looking at data for an 8bpp palette color mode.
That’s neither 8bpp grayscale mode nor 24bpp RGB. It’s almost sure you won’t need to use that.
Just grabbed something to elicit your next paragraph
@fct wrote:
All the technical information you need to understand how TWAIN works is in the specification. EZTwain classic implements parts of it, but just reading the source (or the TWAIN.H header) won’t cut it if you need to extend EZTwain.
So it gives all ( *ALL* ) [in][out]? ( don’t use that syntax, here for clarity ) I use as in the code you posted somewhat down the page. What is at issue here ( I did extract the text of the spec – and have it where I can find it ) is reading those specs too often do not have enough of the information that is in the headers ( #defines as paramater values ), thus results do not always have enough information to disentangle things like the poster I was just reading on The Code Project who had struggles trying do get the vals passed into the message loop and what they convey.
I guess I am in a professional grade of work that I am not normally encountering.
Your work is remarkable, I do not know if I will need to extend EZTwain as I have not made enough progress to report. I knew the code snip I pulled probably had the wrong bpp and so on, sorta what we get to here to be effective is a 0-1-2-3-4-5- do this do that to get a basic grayscale from what amounts to beginner grade work, doing that without knowing what ( coder ) doing. Writing code is vastly more powerful than pushing a few reset buttons on the front panel…..
@fct wrote:
From the EZTWAIN.H header:
.....
// This affects AcquireNative, AcquireToClipboard, and EnableSource.
...
Okay, that’s where I’m gonna start.
@fct wrote:
Also, sorry. SetIndicators is a function I implemented myself, it’s not in the EZTwain code you downloaded. But anyway it’s mostly one line using the CAP_INDICATORS capability and the TWAIN_SetCapOneValue function.
?
@fct wrote:
Then consider implementing either buffered or direct to disk transfers.
Can that be done with a call you have already implemented in EZTwain?