makes sense... I bet implementing it the same routine for gb.gtk would work.
On Thu, Jul 24, 2008 at 7:35 AM, Benoit Minisini
<[EMAIL PROTECTED]> wrote:
> On jeudi 24 juillet 2008, M0E Lnx wrote:
>> Ok... after some more testing, I think I may have miss-stated the facts
>> here.
>>
>> Print sCMD d
On jeudi 24 juillet 2008, M0E Lnx wrote:
> Ok... after some more testing, I think I may have miss-stated the facts
> here.
>
> Print sCMD does print the entire string. Now I'm leaning towards
> believing this is yet another bug in the gtk component
> message.info(sCMD) is what only shows the shorte
Ok... after some more testing, I think I may have miss-stated the facts here.
Print sCMD does print the entire string. Now I'm leaning towards
believing this is yet another bug in the gtk component
message.info(sCMD) is what only shows the shortened string.
Does not happen when using gb.qt. Only
M0E Lnx wrote:
> I just tried that, and I get the same results. I dont know what the problem
> is..
>
> sCMD = "lzmadec " & chr(60) & space(1) & sFilePath
>
> for degbuggind, I print sCMD and all I get is "lzmadec". I can print
> sFilePath and I know for a fact is has a value.
>
How about this:
I just tried that, and I get the same results. I dont know what the problem is..
sCMD = "lzmadec " & chr(60) & space(1) & sFilePath
for degbuggind, I print sCMD and all I get is "lzmadec". I can print
sFilePath and I know for a fact is has a value.
On 7/23/08, Caveat <[EMAIL PROTECTED]> wrote:
>
Have you tried Chr$(60)?
Chr$(33) = ! Chr$(34) = " Chr$(35) = # Chr$(36) = $
Chr$(37) = % Chr$(38) = & Chr$(39) = ' Chr$(40) = (
Chr$(41) = ) Chr$(42) = * Chr$(43) = + Chr$(44) = ,
Chr$(45) = - Chr$(46) = . Chr$(47) = / Chr$(48) = 0
I'm writing an application that uses a shell like to perform some tasks.
I need to parse something like "lzmadec < " & sPath to the shell. The
problem is,
it seems that gambas is only parsing "lzmadec" and ignores everything
starting at the "<" to the end of the line.
I tried escaping the "<" li
