don't show progress bars for short operations

[Martin Pool]

David I points out in <https://bugs.edge.launchpad.net/bzr/+bug/387717> and related conversations that it may be better not to show progress bars for very short operations, otherwise it just looks 'flickery' and it's not really showing the user meaningful progress. It can be hard to tell in advance whether an operation will take a long time. We could for instance suppress the progress bar until at least 500ms has elapsed since bzr started, or since the current operation started.

[Robert Collins (lifeless)]

We used to have debouncing on progress bars, has this gone away somehow?

[Martin Pool (mbp)]

It's still there, this is asking for a tweak to it. I think there's no
hysterisis before initial display.

On Jul 6, 2009 4:30 PM, "Robert Collins" <email address hidden> wrote:

We used to have debouncing on progress bars, has this gone away somehow?

-- don't show progress bars for short operations
https://bugs.launchpad.net/bugs/395998 You receiv...

[Robert Collins (lifeless)]

On Mon, 2009-07-06 at 12:57 +0000, Martin Pool wrote:
> It's still there, this is asking for a tweak to it. I think there's no
> hysterisis before initial display.

Well, there definitely *used* to be. We had bugs that no bars were
shown, whose root cause was that the bar operations in the first
fraction of a second were not shown, and then we got into network ops
which blocked for 10+seconds while ssh handshaking took place.

So, I think that network ops should *not* be hidden in short operations.
I think its fine for the local transport to hide notifications in short
operations, because they rarely block for long periods.

-Rob