On Monday, November 18, 2013 08:09:41 AM André Somers wrote:
It is *not* called by setValue. That is a Good Thing(TM).
I strongly encourage reading code or documentation before making such
answers...
\warning If the progress dialog is modal
(see QProgressDialog::QProgressDialog()),
David Faure schreef op 20-11-2013 12:30:
On Monday, November 18, 2013 08:09:41 AM André Somers wrote:
It is *not* called by setValue. That is a Good Thing(TM).
I strongly encourage reading code or documentation before making such
answers...
Oops...
/me goes to hide quietly in a corner and be
Den 18-11-2013 08:59, Mandeep Sandhu skrev:
You have two viable approaches here:
* break up the saving method into chunks. That is, do a small part of the
work of the saving, queue the next piece of work to be done, and return to
the eventloop. The eventloop will then trigger the next queued
Bo Thorsen schreef op 18-11-2013 9:27:
Den 18-11-2013 08:59, Mandeep Sandhu skrev:
You have two viable approaches here:
* break up the saving method into chunks. That is, do a small part of the
work of the saving, queue the next piece of work to be done, and return to
the eventloop. The
Etienne Sandré-Chardonnal schreef op 15-11-2013 14:05:
Dear all,
I have a long file saving function (gigabytes - several minutes) and I
am trying to use QProcessDialog. I am using it the Modal way as
explained in the documentation. However, the dialog appears after
about 50 seconds, despite
Hi,
it is always safe to call processEvents yourself. If the QProgressDialog has
display issues it obviously does not get enough CPU to update itself, calling
processEvents more often may(!!) help.
When I want to see a QProgressDialog early I normally force the issue by
calling show()
On segunda-feira, 18 de novembro de 2013 08:15:48, Konrad Rosenbaum wrote:
it is always safe to call processEvents yourself.
No, it's not. There are a lot of situations when doing that will cause you
problems elsewhere.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect
You have two viable approaches here:
* break up the saving method into chunks. That is, do a small part of the
work of the saving, queue the next piece of work to be done, and return to
the eventloop. The eventloop will then trigger the next queued piece of the
work being done. This way,
Dear all,
I have a long file saving function (gigabytes - several minutes) and I am
trying to use QProcessDialog. I am using it the Modal way as explained in
the documentation. However, the dialog appears after about 50 seconds,
despite having set the minimumDuration to 0, and called setValue()
