On Friday, 4 de February de 2011 14:06:58 Dawit A wrote: > BTW, there is one side issue I noticed in QProcess through this whole > process. Why does QProcess not exit immediately if I invoke kill or > terminate or even when it just timed out from waiting for the child > process ? IOW, why wait some more for the child process to exit under > those circumstances ? That is what unnecessarily prolongs or even > doubles the blocking period.
kill() or terminate() just send the signals. There's no guarantee that the
process will exit immediately, so why should QProcess notify you of that
immediately? This is especially true for SIGTERM, since that one can be caught
and handled.
--
Thiago Macieira - thiago (AT) macieira.info - thiago (AT) kde.org
Senior Product Manager - Nokia, Qt Development Frameworks
PGP/GPG: 0x6EF45358; fingerprint:
E067 918B B660 DBD1 105C 966C 33F5 F005 6EF4 5358
signature.asc
Description: This is a digitally signed message part.
