- Topics - 9
- Replies - 583
- Total Posts - 592
you can ‘request’ that a driver not display it’s UI with the appropriately named ShowUI parameter in EnableDs. And you can ‘request’ that process indicators not be displayed with Cap_Indicators if your device supports it.
My experience is that the requests are often overlooked and that MessageBoxes will still clutter your OpenDs, EnableDs & EnableDsUiOnly triplets.
The only solution that I have found is to add a boxEater to your app, which is essentially a cbthook running on a seperate thread watching for dialogs you know would like to close. My solution is to set the hook before any of the 3 triplets I mentioned and to unhook after they complete or when you call CloseDs if it is still enabled. On every window activation I check the window title and all of the child controls against a list that I load of dialogs that should have something done to them. The effect is that you have a training stage where you teach your app what dialogs to do stuff to by intentionally jamming paper, unplugging the device, poring coffee on it (ok, not that one), etc