<x-flowed>
At 02:28 AM 9/3/2003 -0700, you wrote:
>I was wrong. I just checked and every parameter is wrapped in double
>quotes. This one needs to be investigated within CVProxy to make sure it's
>receiving the right parameters (i.e. all in double-quotes). If so, then
>the parameter parser in CVProxy may be fumbling things. If you're using
>the parser code I wrote, let me know and I'll take a look at it to fix this.
Oh, this is good. This is just great.
I just renamed my 'CardVault' directory to 'Card Vault', and ran the
example custom extension that shows you the command line parameters (in the
'examples for authors' data files). Guess what the first parameter was?
vault\data\examples\extension.exe
The first parameter on the parameters line is the location of the program
(which is a standard thing everywhere, from what I remember). However, it
looks like it isn't being enclosed in quotation marks, even though it has a
space in it. So CVProxy (and your custom extension) are picking it up as 2
parameters.
I wonder if when we generate the command line, if we enclose the executable
name in ""s, that'll help? I'll try that now.
--
Colen McAlister (colen@wolflair.com)
Lone Wolf Development www.wolflair.com
</x-flowed>
At 02:28 AM 9/3/2003 -0700, you wrote:
>I was wrong. I just checked and every parameter is wrapped in double
>quotes. This one needs to be investigated within CVProxy to make sure it's
>receiving the right parameters (i.e. all in double-quotes). If so, then
>the parameter parser in CVProxy may be fumbling things. If you're using
>the parser code I wrote, let me know and I'll take a look at it to fix this.
Oh, this is good. This is just great.
I just renamed my 'CardVault' directory to 'Card Vault', and ran the
example custom extension that shows you the command line parameters (in the
'examples for authors' data files). Guess what the first parameter was?
vault\data\examples\extension.exe
The first parameter on the parameters line is the location of the program
(which is a standard thing everywhere, from what I remember). However, it
looks like it isn't being enclosed in quotation marks, even though it has a
space in it. So CVProxy (and your custom extension) are picking it up as 2
parameters.
I wonder if when we generate the command line, if we enclose the executable
name in ""s, that'll help? I'll try that now.
--
Colen McAlister (colen@wolflair.com)
Lone Wolf Development www.wolflair.com
</x-flowed>