We use the TImageEnMIO component to allow our customers to scan documents into our software. We recently upgraded our ImageEn components from v. 3 to v. 4.1.0. We allow the customers to use the duplex setting, using the command TImageEnMIO.TWainParams.DuplexEnabled := true.
After making this upgrade, two of our customers have reported that the duplex setting is being ignored. One of them is using a Kodak i1220 and the other is using a Kodak i2400. They have the latest drivers for these scanners. Were there any changes in this version that would prevent us from overriding the scanner's default duplex setting in some situations?
We were not able to recreate the issue here either. But we now have 4 different users reporting this problem, all using different scanners. We tried updating to 4.1.3, but they are still having the problem.
Is there anything that might have been changed that could cause this? Is there any settings or properties we can try to retrieve when they try to scan that could help figure out what the problem is? If we can't find a solution to this, we will have to revert to the earlier version of the component that was not having the problem.
We are using Delphi XE. After we added the line of code to create the twain log, the customer is no longer getting the duplex error. We didn't make any changes other than adding the one line setting the LogFile property. Perhaps there is a variable somewhere that isn't always getting initialized?