> ES> Anyone know how to handle accepting long file names on the command
> line?
> I know that if I want to *FEED* a long file name with
> embedded spaces to another program I should enclose it in
> quotes - for example, at a DOS prompt I can type CD "Program
> Files" to change to that dir.
> However, when I port that editor into 32-bit and associate
> .TXT files to the new 32-bit version, when I double click
> "Read Me Now.txt" in explorer, I get error "File not found:
> Read". My program is parsing paramstr(1) ('Read') as
> unrelated to paramstr(2) ('Me') etc.
Just an approach, but I'd assume that Windoze is passing the string as
separate paramstr[]. I's just code it to add all of the paramstr[] into one
string, i.e. LongFileName:= paramstr[1]+paramstr[2]+paramstr[n]
and use switches after the name for anything else (the '/' symbol)
Hope that gives an idea...
Sean
--- System Support BBS
---------------
* Origin: System Support BBS (1:202/1609)
|