With a debugger... I can see qDebug() outputs fine, that is not the problem.Originally Posted by seneca
With a debugger... I can see qDebug() outputs fine, that is not the problem.Originally Posted by seneca
Reading all output at once, even after the application is finished is not a very good idea. For short outputs it is fine, but if you expect a large amount of data to come through that pipe, you should use a signal/slot mechanism to read the data as it comes in. Why? Because it may happen that you fill the pipe buffer between those two processes and the child process will never finish, because it'll be waiting until some of the buffer is read so that it can write all the remaining data. So you should use readyReadStdout() and family.
My point is, that I never get any output on windows with the above code.
Even when I set the working dir so that the output is expected to be extremely short.
Because there is no "dir" executable on Windows. "dir" is a command.com (or cmd.exe) command, so you have to run it from the shell. There are threads on this forum that cover the topic, maybe you should take a look at them.Originally Posted by jpn
jpn (3rd March 2006)
Ahh, now I get the point..Originally Posted by wysota
Bookmarks