Re: [PyQt] isRunning() returns true after QThread completion

2012-03-05 Thread Hans-Peter Jansen
On Tuesday 28 February 2012, 21:08:46 Lars Beiderbecke wrote: > Hello Hans-Peter, > > Thanks for your answer! The connection type default > Qt.AutoConnection should be equivalent to Qt.QueuedConnection, which > in turn should be the right kind of connection to avoid race > conditions. With both t

Re: [PyQt] isRunning() returns true after QThread completion

2012-02-28 Thread Lars Beiderbecke
Hello Hans-Peter, Thanks for your answer! The connection type default Qt.AutoConnection should be equivalent to Qt.QueuedConnection, which in turn should be the right kind of connection to avoid race conditions. With both types, however, I do experience a race condition. With type Qt.DirectConn

Re: [PyQt] isRunning() returns true after QThread completion

2012-02-26 Thread Hans-Peter Jansen
Dear Lars, On Sunday 26 February 2012, 15:55:25 Lars Beiderbecke wrote: > Hello, > > In my application some QThreads still return isRunning() == true when > they should be completed. > > More specifically, I'm using QThreads to load images asynchronously > in the background. By emitting a signal,

[PyQt] isRunning() returns true after QThread completion

2012-02-26 Thread Lars Beiderbecke
Hello, In my application some QThreads still return isRunning() == true when they should be completed. More specifically, I'm using QThreads to load images asynchronously in the background. By emitting a signal, the thread notifies the main window that the pixmap has been loaded and the correspo