Re: [PyKDE] QThread run() method not being called when start() is executed (PyQt4/ Windows XP)

On 05.03.07 14:32:13, Tony Cappellini wrote: > >Fix your code or post your code. > >Sorry I can't give a more specific answer - a more specific question would > >help. > > Not sure how more specific I could get. The run() method isn't being > invoked, and I don't know how to debug a thread issue.

Re: [PyKDE] QThread run() method not being called when start() is executed (PyQt4/ Windows XP)

Hello Phil, Fix your code or post your code. Sorry I can't give a more specific answer - a more specific question would help. Not sure how more specific I could get. The run() method isn't being invoked, and I don't know how to debug a thread issue. As you requested, here's my code. class Co

Re: [PyKDE] QThread run() method not being called when start() is executed (PyQt4/ Windows XP)

On Monday 05 March 2007 6:49 am, Tony Cappellini wrote: > This is the first time I've used QThreads, and it's not going well. > The run method is not being called after start() is executed. > > What are some possible explanations for this? Your code is wrong. > What can I do to debug this kind of

[PyKDE] QThread run() method not being called when start() is executed (PyQt4/ Windows XP)

This is the first time I've used QThreads, and it's not going well. The run method is not being called after start() is executed. What are some possible explanations for this? What can I do to debug this kind of problem? ___ PyKDE mailing listPyKD

[PyKDE] QThread, signals and slots

Hi, I have a problem with passing signals a cross threads. I was under the impression that when using Qt.QueuedConnection the slot would always be executed in the thread that the receiver object lived. But when I created this test application I does not seem to be doing that. Any suggestions on

Re: [PyKDE] QThread

> right after finishing my work on a make-shift > process-spawning-and-killing-framework to have concurrent threads that can > be terminated to circumvene the lack of such a feature in the python > threading model, I discovered QThread. Now I wonder if my work is totally > obsolete, or if there are

[PyKDE] QThread

Hi, right after finishing my work on a make-shift process-spawning-and-killing-framework to have concurrent threads that can be terminated to circumvene the lack of such a feature in the python threading model, I discovered QThread. Now I wonder if my work is totally obsolete, or if there are

Re: [PyKDE] QThread gone?

> > > > What happened? If QThread isn't there anymore, what's the alternative? > > Thread support is determined when you build PyQt. Check the messages that > were displayed. > > Phil > Thanks, Phil. I am indeed a slobbering waterhead; I'll read the build instructions next time ;-) Eric

Re: [PyKDE] QThread gone?

On Friday 21 November 2003 1:30 am, Eric Williams wrote: > Hi there, > > I've just installed the new version of PyQt (PyQt-x11-gpl-3.8.1), and now > my program doesn't work anymore. It fails with the following: > > Traceback (most recent call last): > File "./QSynclogs.py", line 27, in ? > i

Re: [PyKDE] QThread gone?

On Fri, Nov 21, 2003 at 02:30:42AM +0100, Eric Williams wrote: > > What happened? If QThread isn't there anymore, what's the alternative? > QThread is there, but you need to build it against qt-mt, and not qt. Pass "-l qt-mt" to build.py to force this behaviour. ___

[PyKDE] QThread gone?

Hi there, I've just installed the new version of PyQt (PyQt-x11-gpl-3.8.1), and now my program doesn't work anymore. It fails with the following: Traceback (most recent call last): File "./QSynclogs.py", line 27, in ? import FTPWorker File "/home/eric/Desktop/Data/Dev/Python/QSynclogs/F