- This topic has 0 replies, 1 voice, and was last updated 14 years, 10 months ago by .
-
Posts
-
To say that I don’t like the way dialog boxes are used by some of the vendors doesn’t give my frustration enough credit. I’ve run across several drivers (coughEpsoncough) that insist on displaying an error dialog that must be closed before the ds will fail the previous call. Mostly these get in the way following/during OpenDs calls but I see a fair number of them during/while EnalbeDs and EnableDsUiOnly.
I have a winapi solution to this problem that uses known dialog box information to look for then close known dialogs when I execute a few twain calls. This is a tedious workaround, especiallyt the ‘known’ part. without knowledge of the dialog that the source pops up when their hardware isn’t turned on i can’t stop the dialog. I wish I could say the vendor isn’t following the spec, but every place in the spec i see mention of an error dialog, the spec gets all wishywashy and seems to say that if the vendor wants to make you click on something that its all right.
I’m curious, anyone else have another solution? How is anyone else dealing with unwanted twain dialog boxes?