My main window has a progress bar in it. When I click a button my script
starts a thread for a backend script that takes some time to run.
The backend script passes data including its progress to my main script via a
FIFO, now I have a problem.
The FIFO is providing progress data that is being
On Sunday 24 September 2006 12:55, Dave S wrote:
My main window has a progress bar in it. When I click a button my script
starts a thread for a backend script that takes some time to run.
The backend script passes data including its progress to my main script via
a FIFO, now I have a problem.
On Sunday 24 September 2006 13:44, Andreas Pakulat wrote:
On 24.09.06 13:16:11, Detlev Offenbach wrote:
On Sunday 24 September 2006 12:55, Dave S wrote:
My main window has a progress bar in it. When I click a button my
script starts a thread for a backend script that takes some time to
24 Eyl 2006 Paz 15:38 tarihinde, Detlev Offenbach şunları yazmıştı:
[...]
Try QApplication.processEvents() after the setProgress call.
Or use events to communicate the progress. I haven't had the experience
yet, but many qt and kde developers say that processEvents is evil and
should
Ismail Donmez wrote:
Or use events to communicate the progress. I haven't had the
experience yet, but many qt and kde developers say that
processEvents is evil and should be avoided, it might have
mysterious side effects.
Which ones?
If you used deleteLater() for an QObject,
24 Eyl 2006 Paz 17:05 tarihinde şunları yazmıştınız:
Ismail Donmez wrote:
Or use events to communicate the progress. I haven't had the
experience yet, but many qt and kde developers say that
processEvents is evil and should be avoided, it might have
mysterious side effects.
Which
