Welcome Guest! To enable all features, please Login or Register.



Last Go to last post Unread Go to first unread post
#1 Posted : Wednesday, April 16, 2008 7:18:16 AM(UTC)

Groups: Registered
Posts: 11


    What exactly this flag does and affects? There is nothing in documentation except that this invokes "native transfer". What is "native transfer"?

Try the latest version of LEADTOOLS for free for 60 days by downloading the evaluation: https://www.leadtools.com/downloads

Wanna join the discussion? Login to your LEADTOOLS Support accountor Register a new forum account.

#2 Posted : Wednesday, April 16, 2008 10:39:56 AM(UTC)


Groups: Tech Support
Posts: 366

Thanks: 1 times
Was thanked: 4 time(s) in 4 post(s)

There are two very basic types of data transfers that every TWAIN Source must provide: Native and Buffered memory. A native data transfer is like the buffered memory transfer in that it deals with memory. The difference is that a native transfer allocates a whole block of contiguous memory and is limited to the DIB or PICT formats. This can be problematic if you have a limited amount of memory to work with, or the memory that you have is fragmented. The transfer will fail if a large enough block of memory is not available. The native transfer is set as the default and is the easiest to implement. If a different transfer is needed, capability negotiation will be required for the change. The transfer allocates a single block of memory to write the image to and then passes a pointer to the calling application. It is the application's responsibility to free that memory when done with it.
The other transfer type defined by TWAIN, disk file, is not required to be provided by the Source. It allows for images to be written to disk. The application must first create an image file that the Source can handle and assure that it is accessible. The Source has a capability that specifies file formats which can be used. The application can then set the file format and the file name to be used. The application must be able to manage the file after it is created.
Disk file transfers are ideal for large and very large images where native transfers are unrealistic. A disk file transfer is a little more difficult to implement than a native transfer but easier than a buffered memory transfer. This type of transfer is the slowest of the threes as well since it is dealing with the a hard disk as opposed to system memory.
Walter Bates
Senior Support Engineer
LEAD Technologies, Inc.
You cannot post new topics in this forum.
You cannot reply to topics in this forum.
You cannot delete your posts in this forum.
You cannot edit your posts in this forum.
You cannot create polls in this forum.
You cannot vote in polls in this forum.

Powered by YAF.NET | YAF.NET © 2003-2023, Yet Another Forum.NET
This page was generated in 0.075 seconds.