STRBUFFER

[ReDFlaG]

Hello,

Here's a piece of my code.

$foo = Run(".\prog.exe /d", "", @SW_HIDE, $STDERR_CHILD + $STDOUT_CHILD)
$line = StdoutRead($foo)

Very simple isn't it? The problem is that the string that is returned by the prog is bigger than the size of a general string buffer limitation (4095 chr). So i got a part of it....

How can i increase the buffer size so that i can handle the whole string?

Thanks

[DaveF]

Hello,

Here's a piece of my code.

$foo = Run(".\prog.exe /d", "", @SW_HIDE, $STDERR_CHILD + $STDOUT_CHILD)
$line = StdoutRead($foo)

Very simple isn't it? The problem is that the string that is returned by the prog is bigger than the size of a general string buffer limitation (4095 chr). So i got a part of it....

How can i increase the buffer size so that i can handle the whole string?

Thanks

Does this work?

Dim $line
  $foo = Run(".\prog.exe /d", "", @SW_HIDE, $STDERR_CHILD + $STDOUT_CHILD)
  While 1
    $line &= StdoutRead($foo)
    If @error = -1 Then ExitLoop
  WEnd

The above assumes that your own script is more-or-less complete and that the child prog.exe will exit while we're reading the data; when it exits it will close its STDOUT pipe and a final call to StdoutRead will return empty and set @error to -1. If your script is a script fragment then you could just call StdoutRead several times or use a While loop like the above and test the size of $line at the top of the loop...

[ReDFlaG]

It works, &= was the key.

I presume that the prog send a part of the datas, then relaunch itself to send another part, so if not using &=, only first wave of datas was in the $line. (while using $= 'add' all parts until prog is over).

Did i get it?

Thank you very much

[DaveF]

It works, &= was the key.

I presume that the prog send a part of the datas, then relaunch itself to send another part, so if not using &=, only first wave of datas was in the $line. (while using $= 'add' all parts until prog is over).

Did i get it?

Thank you very much

Well, maybe not relaunch, but it could have been two or more seperate "prints" or you may have had it in your first post; the prog wrote as much as it could until its STDOUT buffer filled up, then waited until AutoIt could read the data and empty the buffer before writing again. Don't know without knowing how the child program is put together...