Okay I looked at the example:
> http://pastebin.com/f16019559
and it appears that Bridge is a little bit unnecessary when you could
just emit the signal from your QThread as it is?.
So I tried to make an example following what you did;
http://pastebin.com/m192d4d3f
That brings me to a ques
On Wed, Oct 8, 2008 at 5:16 PM, Mistobaan <[EMAIL PROTECTED]> wrote:
>> http://pastebin.com/f16019559
>
> I am wrong or the line 21 never gets called, so everything still happens on
> one single thread?
it's started after Gamepad.start() which trigger Gamepad.run() then...
i have it in commented c
http://pastebin.com/f16019559
I am wrong or the line 21 never gets called, so everything still
happens on one single thread?
Fabrizio
___
PyQt mailing listPyQt@riverbankcomputing.com
http://www.riverbankcomputing.com/mailman/listinfo/pyqt
this is how i solved my problem... i run the non-qt process as thread
and inherit class Bridge which emits the Qt signals for me... hope it
will help you:
http://pastebin.com/f16019559
i'm sure there are more elegant solutions and i would like to learn
about them...
__
On 10/06/2008 11:57 PM, Matt Smith wrote:
> > I have written an app for checking my email, and it laggs when I am
> > downloading from the server and I am curious how to avoid this.
> >
[...]
> > I double click the MailBoxList it emits a signal that Email Widget is
> > connected to which then call
I have written an app for checking my email, and it laggs when I am
downloading from the server and I am curious how to avoid this.
The general layout is
EmailWidget (Qwidget with a layout)
.ImapTool
.MessageList(QlistView)
.MailBoxList(QlistView)
def RefreshMessag
