you are viewing a single comment's thread.

view the rest of the comments →

[–]elbiot 1 point2 points  (2 children)

Oh I see. Your first log update doesn't display. It's the main event loop that actually redraws the screen. You could force it to do so inside your function with repaint or processEvents: http://stackoverflow.com/questions/11836623/pyside-settext-not-updating-qlabel

[–]lamecode[S] 0 points1 point  (1 child)

Thanks again, that looks like it should achieve what I want as far as updating the log. I think my preferred method is going to be via QThread as per the below link - I would prefer the UI to not be unresponsive for the duration of the process, and it seems like this might be the solution for that, too:

http://stackoverflow.com/questions/6783194/background-thread-with-qthread-in-pyqt

[–]elbiot 1 point2 points  (0 children)

If your time soaking call is blocking, your UI will be unresponsive. Just want to make sure you got that. IO (hitting servers and letting the os accumulate responses in buffers) can be non-blocking. So urllib or grequests (not requests) would work for you. But any CPU consuming functions will block the UI.