| T O P I C R E V I E W |
| FabioDefferrari |
Posted - Jun 24 2024 : 11:04:46
Hi, I’m having a problem while calling the IO.Acquire method, when the acquisition dialog opens behind the form where the TImageEn object is placed.
As long as I’ve found out, is happens when the component is set to Visible=False
Any idea how to avoid that? |
| 6 L A T E S T R E P L I E S (Newest First) |
| FabioDefferrari |
Posted - Jul 05 2024 : 13:25:34
Nigel
I ended up using TImageEnIO component instead of TImageEnMView, and it worked out fine. |
| xequte |
Posted - Jun 26 2024 : 23:49:33
Yes, sorry, should have mentioned that.
What happens with multiBmp.MIO.Acquire()?
Nigel
Xequte Software
www.imageen.com
|
| FabioDefferrari |
Posted - Jun 26 2024 : 12:50:35
Nigel, sorry for the question: to use MIO under TIEMultiBitmap, I should just add iexHelperFunctions in uses clause, right? Or do I have to do something else?
UPDATE: solved. |
| xequte |
Posted - Jun 25 2024 : 16:10:26
Thanks Fabio,
We'll look into that shortly. Do you see the same issue if you use a TIEMultiBitmap instead of TImageEnMView?
e.g. multiBmp.MIO.Acquire();
http://www.imageen.com/help/TIEMultiBitmapHelper.MIO.html
Nigel
Xequte Software
www.imageen.com
|
| FabioDefferrari |
Posted - Jun 25 2024 : 08:36:41
Hi, Nigel
I haven't tried with Twain, but in WIA scanners it always happen.
It doesn't happen in the Demo app, probably because the TImageEnMView component is set to Visible=True.
For now, I "solved" by setting Visible to True and setting Height/Width to 0 (zero), so the object isn't visible on form to the user. But I believe the "Visible" property shouldn't make a difference in the way the acquisition dialog is shown, right? |
| xequte |
Posted - Jun 24 2024 : 15:02:48
Hi Fabio
Does it only happen with a particular scanner driver, or all scanners called from that application?
Does it also happen in our demo applications, such as AllAcquire.dpr?
Nigel
Xequte Software
www.imageen.com
|
Search
