On Tue, 29 Feb 2000, Roberto Alsina wrote:

> 
> So, in the end, the question is: should it BE fast, or FEEL fast? It's a
> tough choice :-)

Make it *be* fast. But add intelligence to the show()/hide() method of the
progressbar. If the first value transmitted by the loader signal to the
progressbar's slot (or the slot that shows the bar, in fact :-) is very
hight, don't show yet the bar. Wait for a second signal and if this is
"100%" (or very near :-) forget about the bar (anyways this means the user
has already what he wanted). Otherwise, show the bar with the proper
value.


Of course you have to decide and experiment thresholds: above what value
of the signal is it ignored? (50%? Perhaps. If the first signal announces
50%, then good chances are the loading finishes before the next signal
comes)

Big problem. If you don't get percents of the loading process, or even
worse, if you don't know how much would be to get loaded in the end ....

Cristian