- Topics - 1
- Replies - 5
- Total Posts - 6
gabe, thank you very much for your clarification of EnableDsUiOnly process! If I got it correctly, I might solve my problem by presenting user with EnableDsUiOnly dialog, after he clicks “OK” I retrieve the values user just set by using CustomDsData/Get. Right after that, I use CustomDsData/Set to send those values to scanner and then start acquiring process without GUI. So to user it would seem that they just entered values and started scanning.
But, if I run into device that doesn’t support CAP_ENABLEDSUIONLY, I need to have a fallback strategy using cap-by-cap approach. What is the widespread of CAP_ENABLEDSUIONLY capability these days? Is it reasonable to expect that most (every?) devices out there support it?
What I’m trying to achieve is following: when user first opens GUI, it sets some data (brightness, contrast, width, height, color, …) that I save to his profile. Then he scans images and closes application. After that, the next time the same user opens GUI, I want to “prepare” GUI with values from his previous session.