[Qt-interest] Advise on how to prevent GUI lockout
David Boosalis
david.boosalis at gmail.com
Sat Aug 14 18:06:06 CEST 2010
A while back (it was more then once) I was asking how to speed up delays
found between QTcpServer and QTcpSocket. Well the problem was really more
of a Tcp issue. The solution was to use multiple sockets and distribute the
date sent among them. This works great, and in a few corner cases it works
to good. The data rate overwhelms the poor Qt application causing the GUI to
be locked and frozen as it cannot keep up with all the draw requests (The
CPU usage for the application goes up to 100%).
I would like to know what is the best practise for handling this kind of
problem. Ideally I'd like to peak at the event queue to see how many request
are pending. If to many, tell the class holding the socket to start
buffering the data. The QAbstractEventDispatcher class looked like it might
help me but there are not any examples of this, and maybe there is an easier
way.
Has anyone dealt with this issue, if so I 'd appreciate hearing how you
resolved it.
Thanks
David
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.qt-project.org/pipermail/qt-interest-old/attachments/20100814/5fcc0b13/attachment.html
More information about the Qt-interest-old
mailing list