- Topics - 9
- Replies - 583
- Total Posts - 592
ok, this is going to be slightly offtopic.. but here it is.
it isn’t new. introduced in (I think) the 1.7 spec EnableDsUiOnly allows you to retrieve all of the settings from the vendor as (basically) a string. It is used (at least by me) for building a profile of the settings I want to use for an acquisition.
Following EnableDsUiOnly the standard vendor Ui comes up, but when the user Oks the Ui instead of an acquisition starting (as is the case with EnableDs) you are able to query for the settings with CustomDsData/Get.
The idea is that you often only have a handful of settings you want to scan with -say high, medium, low, full color & blackWhite (you may have others, but follow the idea).
Users are able to use the Vendors Ui to specify what they want. You pull and store the settings. Then later when they want to scan something, instead of you manipulating the settings (as you are today when you set the brightness) you just send CustomDsData/set with the string you pulled eariler with CustomDsData/Get.
Following this kind of profile based approach you no longer need to manipulate caps one-by-one.
Plus for day-to-day production use they no longer have a chance or risk of scannign with incorrect values.
If your devices support EnalbeDsUiOnly and CustomDsData (and if the twister reports are correct) then this is imho a much better model for cap negotiation.
now back to your question. Is there a setting for brightness in the Vendor Ui? And more importantly, does it make sense in your use to have the users use that settings instead of setting brightness by hand or do you really really need to set the brightness by hand?