CLI does not support all profile options as commandline options OR specifiy a profile file as option that is not necessarily in the user's folder, but can be anywhere #404
Is your feature request related to a problem? Please describe.
When creating a script for NAPS2, using the CLI I found that it was not possible to set all options that are provided by NAPS2 in a profile. So I wondered how go on, needing some of these parameters.
Giving a name of an existing profile that was set up in GUI is a bit contrary to the idea of using a command line tool.
Especially when I have to distribute the script to different users that can not handle setting the profile up by themselves. Not to speak if the profile needs some modifications.
Describe the solution you'd like
All options that are provided by a profile should also be accessible as a command line parameter to NAPS2.console.exe
Describe alternatives you've considered
An alternative approach would be to give the NAPS2.console.exe an option that refers to a profile.xml file that does not have to be under the user's application folder, but anywhere. So it would be possible to distribute profiles alongside with the script. Which would also be fine.
Is your feature request related to a problem? Please describe. When creating a script for NAPS2, using the CLI I found that it was not possible to set all options that are provided by NAPS2 in a profile. So I wondered how go on, needing some of these parameters. Giving a name of an existing profile that was set up in GUI is a bit contrary to the idea of using a command line tool. Especially when I have to distribute the script to different users that can not handle setting the profile up by themselves. Not to speak if the profile needs some modifications.
Describe the solution you'd like All options that are provided by a profile should also be accessible as a command line parameter to NAPS2.console.exe
Describe alternatives you've considered An alternative approach would be to give the NAPS2.console.exe an option that refers to a profile.xml file that does not have to be under the user's application folder, but anywhere. So it would be possible to distribute profiles alongside with the script. Which would also be fine.
Thanks and best Regards.