[PyQt] Too many signals fired in short timespan: one step closer to solution

Dariusz Makowski dariusz1989 at gmail.com
Wed Jun 13 18:50:18 BST 2018

I think you can specify a time for that processEvents() as well so it 
does larger process than a small one. Maybe that could help?

On 13/06/2018 18:29, kristof.mulier at telenet.be wrote:
> Dear PyQt users,
> I believe we're one step closer to the solution. Please read the 
> *EDIT* at the very end of the StackOverflow question:
> https://stackoverflow.com/questions/50841486/pyqt5-too-many-signals-fired-in-short-timespan-causes-a-stack-overflow
> I noticed that the repeated call to app.processEvents() is the 
> culprit, when called too often in a short timespan. Removing that line 
> from the code in the slot, solved the issue. But it takes down the 
> responsiveness of my GUI. So I thought, why not query first if there 
> are any events to get processed anyway? Unfortunately, the function 
> hasPendingEvents() is not safe to use when there are any 
> non-main-threads running in the entire application. That's not okay.
> Please help...
> _______________________________________________
> PyQt mailing list    PyQt at riverbankcomputing.com
> https://www.riverbankcomputing.com/mailman/listinfo/pyqt

07 590 530 854
Dariusz at Dariuszmakowski.com

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.riverbankcomputing.com/pipermail/pyqt/attachments/20180613/8ee74685/attachment.html>

More information about the PyQt mailing list