[Qt-interest] QLabel is invisible after setText()

[Bruno Colombet]

Le 28/01/2011 14:36, Paul Miller a écrit :
> On 1/28/2011 6:29 AM, André Somers wrote:
>> On Friday 28 January 2011 13:02:07 Bruno Colombet wrote:
>>
>>> Ok thank you for the link.
>>> I'm already using threads in my application. That Widget was just to
>>> warn users for some unresponsive UI during relatively short time.
>> In that case, perhaps a QApplication::processEvents() call is all you need. I
>> am not a big fan of using it in the general case, but to make sure your
>> warning for a short freeze is actually painted, perhaps it would be a
>> solution. A better way is of course to make sure that your UI simply does not
>> become unresponsive, not even for a short while. However, I realize that that
>> is not always feasable.
> I use processEvents() during long waits with a progress bar - works fine.
> But for SHORT waits why not just use a busy cursor? Depends on what you
> mean by short I guess, but for short occasional delays of 1-2 seconds I
> use a wait cursor.
> _______________________________________________
> Qt-interest mailing list
> Qt-interest at qt.nokia.com
> http://lists.qt.nokia.com/mailman/listinfo/qt-interest
Good idea too. But I'd like to inform the user about Why he has to wait 
as it sometines not trivial for the user.
I mean if you explicitly click on a time consuming features, you expect 
the application to be busy, so in that case a busy cursor is ok.
In my case, it's for some particular situation where I must rebuild a 
mesh using a delaunay algorithm, but the user doesn't know that.
So it just displays a message like : Please Wait building mesh... for 
let say 5 seconds.

-- 
Bruno Colombet
*INSERM UMR 751* - Epilepsie et Cognition
Faculté de Médecine
27 Bd Jean Moulin
13385 Marseille cedex 05
+33 4 91 38 55 40
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.qt-project.org/pipermail/qt-interest-old/attachments/20110128/40697041/attachment.html