Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.lang.python > #81654 > unrolled thread

Re: Fwd: Python Signal/Slot + QThred code analysis

Back to article view | Back to comp.lang.python

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.

Contents

  Re: Fwd: Python Signal/Slot + QThred code analysis Juan Christian <juan0christian@gmail.com> - 2014-11-27 23:29 +0000

#81654 — Re: Fwd: Python Signal/Slot + QThred code analysis

[Multipart message — attachments visible in raw view] — view raw

On Thu Nov 27 2014 at 9:16:38 PM Juan Christian <juan0christian@gmail.com>
wrote:
I'll read the code thoroughly and reply to you if I find something strange,
many thanks!


So, instantly I found one issue, you said that this code won't block the
GUI, only the thread event loop, but if we keep moving the window while
it's open, every time new info is printed the GUI freezes for like 1-2
seconds.

And why this approach of a single instance is better? I mean, I'll have to
call Outpost every time I get new data from my other API, because there
will be different users, so I need to create different instances so I call
the site with a new ID, don't I?

Maybe the answer for that question is that you using a timer that is ALWAYS
active and ALWAYS calling the the outpost site, so I'll have something like:

var = Outpost('12345')
var.posts -> 100
var.setID('67893')
var.posts -> 35

Is that right? But I don't think that always calling the site this way is
good for them and for me, sometimes I may not get new users for like 10~15
minutes, so I would have wasted a lot of calls for nothing. That's why I
only instantiate/call the site when I get new users.

[toc] | [standalone]

Back to top | Article view | comp.lang.python

csiph-web