This is a little vague. If you're using the twaincsscan app, then you'll probably be best off using the driver UI built into the vendor's TWAIN driver. If it supports DAT_CUSTOMDSDATA, then you can save snapshots of your changes, and use those when you want to scan.
If you're looking to program with TWAIN CS, then I recommend running the twaincstst app. Once you've opened the driver you want to use, try selecting DG_CONTROL / DAT_CAPABILITY / MSG_GETCURRENT for ICAP_XRESOLUTION, ICAP_SUPPORTEDSIZES and CAP_FEEDERENABLED. The data returned is a CSV representation of the underlying TWAIN structures.
You can refer to the TWAIN Specification at twain.org for more information about those structures.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
This is a little vague. If you're using the twaincsscan app, then you'll probably be best off using the driver UI built into the vendor's TWAIN driver. If it supports DAT_CUSTOMDSDATA, then you can save snapshots of your changes, and use those when you want to scan.
If you're looking to program with TWAIN CS, then I recommend running the twaincstst app. Once you've opened the driver you want to use, try selecting DG_CONTROL / DAT_CAPABILITY / MSG_GETCURRENT for ICAP_XRESOLUTION, ICAP_SUPPORTEDSIZES and CAP_FEEDERENABLED. The data returned is a CSV representation of the underlying TWAIN structures.
You can refer to the TWAIN Specification at twain.org for more information about those structures.