.@qt-project.org
Subject: [Interest] QProgressDialog when setValue(0) is called
Hello All,
I have a class that is inherited from QProgressDialog. It sometimes
crashes and its inside QProgressDialog class code.
I detected that when the setValue(0); is called in its constructor,
crash happens. When I comme
Hello All,
I have a class that is inherited from QProgressDialog. It sometimes
crashes and its inside QProgressDialog class code.
I detected that when the setValue(0); is called in its constructor,
crash happens. When I commented out this function, It does not crash.
Even if setValue(0) is called
Constantin- Thank you for your quick reply.
> Also the case when both minimum and maximum are both set to zero is mentioned
> in QProgressBar's description and I'm not sure it's really necessary to
> duplicate that information for QProgressDialog which is built on top of
> QProgressBar
>
Oops.
That behavior looks reasonable to me -- the dialog must tell the system to
redraw it, but doing that with an unchanged dialog would be waste of time.
And obviously one can't change value of an indeterminate progress
bar/dialog as it doesn't have any value at all. :-)
Also the case when both minimu
The documentation for QProgressDialog doesn't say anything about it, but it
appears that setting both minimum and maximum to zero results in an
"indeterminate" progress dialog. The documentation *does* say that if you make
it a modal dialog, then calling QProgressDialog::setValue() will call
pr
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
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()),
s
> I strongly object to using a thread for something this simple. Threading
> is to be avoided whenever possible, because it's so hard to debug. Use
There's no black magic involved in threads. Though I agree it might be
an overkill in some cases, not so sure about this case.
> the chunks method in
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 eventloo
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 q
> 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,
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
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() immediat
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 h
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() se
15 matches
Mail list logo
