#9 Hard-coded options
Looking at the source code for Encrypt:
The function builds a file named eoptions.txt with
hard-coded options (e.g. force-v3-sigs, etc), saves
the file, and when GPG is invoked, it is directed to
look at that file. The user has no opportunity to
customize these options.
From the perspective of implementing an interface
that complies with the NCHelp requirements, this
works well.
From the perspective of implementing a generic
interface, it doesn't.
It is clearly evident from looking at the code, how
difficult it is to come up with a dll that will
interface silently with gpg.exe. Is it possible to
allow the user to specify an options file, or at least
not hard-code options in the encrypt function, and
provide a sample eoptions.txt file that doesn't get
re-written by the dll?
We could all still comply by using a sample file
based on the currently hard-coded options, but
users not connected with NCHelp in any way won't
be forced to use options they may not want / have
the capability of using additional options that are
currently not there.
Thanks, and sorry for bringing this up so late in the
development phase.
Logged In: YES
user_id=436438
Wouldn't this be avaliable to anyone who wanted to use the
MainExec function? They would need to create the opts file
and the batch file to invoke the GPG exe and just pass the
path+filename of the batch file off to the MainExec function.
If I've mis-understood the request then please help me to
understand better.
I think that better documentation would also help users to
utilize this utility.
John