[prev in list] [next in list] [prev in thread] [next in thread] 

List:       pykde
Subject:    Re: [PyKDE] twisted and PyQt4
From:       Toby Dickenson <tdickenson () devmail ! geminidataloggers ! co ! uk>
Date:       2006-06-01 11:27:03
Message-ID: 200606011227.03727.tdickenson () devmail ! geminidataloggers ! co ! uk
[Download RAW message or body]

On Thursday 01 June 2006 11:24, scalet@yebu.de wrote:
> just for the record,
> 
> I got some replies on the twisted mailing list, now
> they have an experimatal reactor for pyqt4 in there
> tracking system:
> 
> http://twistedmatrix.com/trac/ticket/1770
> 
> I used it and it worked fine, so far

Im not sure which platform you are using, but Ive never had much success with 
this approach on Windows. Your main thread normally spends its time running 
the Qt main loop, however on Windows it is quite legitimate for library 
functions to briefly run their own message loop. Examples include standard 
dialog boxes (file chooser, font chooser etc), MessageBox, and cross-process 
COM method calls. This will cause your twisted reactor to stop processing 
twisted events until control returns to the Qt message loop.

One alternative approach which does integrate well with these secondary 
message loops is Twisted's ThreadedSelectReactor. (I forget whether this is 
released now, or whether you need to grab it from SVN). 

-- 
Toby Dickenson

_______________________________________________
PyKDE mailing list    PyKDE@mats.imk.fraunhofer.de
http://mats.imk.fraunhofer.de/mailman/listinfo/pykde
[prev in list] [next in list] [prev in thread] [next in thread]