Skip to content

Indeterminate ProgressTasks should ignore Value/MaxValue #1907

@RJohnsonPGH

Description

@RJohnsonPGH

Information
Platform independent

Describe the bug
ProgressTasks that are set to be indeterminate will show as completed if Value ever reaches MaxValue. This includes the task being hidden automatically if HideCompleted is set to true.

To Reproduce
Take enumerating a folder for files, for example. I don't know how many files exist until the process is complete. It's indeterminate. In a producer/consumer pattern, I might be processing the files as they are discovered. If the producer is faster than the consumer, there's no problem. MaxValue will increase faster than Value. However, if the two tasks are fairly balanced or if the consumer is faster, Value will match MaxValue.

The end result of this is that the indeterminate task will often show as completed. With HideCompleted the task will flicker as it is constantly being shown and hidden.

Expected behavior
I would think that completion calculations: percentage, the progress bar showing as full and colored as green, the task being hidden if HideCompleted is set, etc. should ignore Value/MaxValue if the task is set to be indeterminate. x


Please upvote 👍 this issue if you are interested in it.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    Status

    Todo 🕑

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions