Jump to content
Sign in to follow this  
baghenamoth

Problem with StdOutRead under 3.2.12

Recommended Posts

baghenamoth

Hi everybody,

I have a pb with StdOutRead function under 3.2.12 :

while looping StdOutRead, it returns constantly the previous value. With previous version of autoit (=>3.2.10) the return is only the last value sent by the child process.

I don't know if this is very clear but here is a exemple :

compile the child process to stdout.exe (which will send to console number + test every second during 20 seconds) :

include-once

For $i = 1 To 20
    ConsoleWrite($i & " TEST" & @CR)
    Sleep(1000)
Next
ConsoleWrite("FINISH")oÝ÷ ØÛh­æ¶¬rì¢W°Øm+,r¸©µ«­¢+Ø¥¹±Õµ½¹(¥¹±Õ±Ðí
½¹ÍѹÑ̹ÔÌÐì)¥´ÀÌØí½¼°ÀÌØí±¥¹(ÀÌØíµå
µ±¥¹ôMÉ¥ÁѥȵÀìÅÕ½ÐìÀäÈíMQ=UP¹áÅÕ½Ðì(ÀÌØí½¼ôIÕ¸ ÀÌØíµå
µ±¥¹°MÉ¥ÁѥȰM]}!%°ÀÌØíMQII}
!%1¬ÀÌØíMQ=UQ}
!%1¤)]¡¥±Ä($ÀÌØí±¥¹µÀìôMѽÕÑI ÀÌØí½¼¤(%%ÉɽÈQ¡¸á¥Ñ1½½À(%
½¹Í½±]É¥Ñ ÀÌØí±¥¹µÀì
H¤(%%ÀÌØí±¥¹ôôÅÕ½Ðí%9%M ÅÕ½ÐìQ¡¸á¥Ñ1½½À)]¹oÝ÷ Ø è¶«ªç¬¶*'"z-Ƕ­o&v)ÚÞ~Þ
, it doesn't return empty strings (under 3.2.12), can someone explain this to me please ?

Here are the result after few seconds with 3.2.12 : with $line &= StdoutRead($foo)

1TEST

2TEST

3TEST

4TEST

5TEST

1TEST

2TEST

3TEST

4TEST

5TEST

1TEST

2TEST

3TEST

4TEST

5TEST

6TEST

Here are the result after few seconds : with 3.2.10 : with $line = StdoutRead($foo)

1TEST

2TEST

3TEST

4TEST

Do you know how to have the same result with 3.2.12.0 ?

Thanks in advance for your answer.

Edited by baghenamoth

Share this post


Link to post
Share on other sites
baghenamoth

Snif, I saw that, this change is actually my pb...

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this  

×

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.