- Topics - 9
- Replies - 583
- Total Posts - 592
…havent found the instructions…
no, they don’t really exist. The commandline sample is a proof of concept and no it doesn’t explore the twain spec quite the way that the winforms sample does, but it uses the same core twain library as the windforms sample – anything the gui can do the cmdline can as well.
brigthness/contrast/dpi/etc – those would be more appropriate for a library that ws built to manipulate the device capabilities one-by-one. The profile driven approach I took has you use the regualar device gui for the setup phase and then the settings that you configured from the gui are run later. I’ve added some of the individual capabilites to the library and will eventually add the whole set (well… maybe not the audio ones..) becasue people keep asking for the ability to configure devices that way but I don’t believe that it is a succuessful model so… I’m doing it but my heart isn’t in it the same way so it’s going real slow. If you want to talk about extending the commandline interface to opentwain send me an email or IM.