Re: [MiNT] some gem question

[mikro <mikro@hysteria.sk>]

> Hmm, so it's Teradesk bug then. What a pity Teradesk is the only desktop
> which supports >128 filenames so I have no chance to test it on some other
> desktop...
>
I have to reply by myself since it's not Teradesk bug but XaAES bug. After
hours of testing I find finally what's wrong:

I think standard way how to handle ARGV is to use it if command line length
is over 125 chars, at least N.AES and XaAES seems to do so (or maybe mintlib
handles it in such way, but the AES is important, see below). If I launch
application (using d&d) with commandline under 125 chars, both XaAES and
N.AES give me argv[0] = "" and argv[1] = "first arg". In case of blanks in
filename, it quotes in '' but this is a job for mintlib to parse it, so no
problem here.

Problem arrives with > 125 chars commandline. In N.AES I get: argv[0] =
application's filename, argv[1] = "first arg" etc... so it's handled
correctly. But in XaAES I see: argv[0] = application's filename (without
path!) argv[1] = "". I didn't test it under magic but I think its behaviour
will be the same as N.AES... So, please, fix it asap, it makes any
application that supports really long names unusable :(

-- 

---------------------------------------------------------------------------
MiKRO         Atari XE/XL/Mega STE/Falcon060         http://mikro.atari.org
---------------------------------------------------------------------------