• I have marked all applicable categories:
  • exception-raising bug
  • [ x] visual output bug
  • documentation request (i.e. "X is missing from the documentation." If instead I want to ask "how to use X?" I understand [StackOverflow#tqdm] is more appropriate)
  • new feature request
• [ x] I have visited the [source website], and in particular
  read the [known iss

Version

v3.0.0

Reproduction link

https://codesandbox.io/

Steps to reproduce

My version is 4. It is not listed in options. I am on windows and i setup as poor ass docs says. Nothing show on console.

What is expected ?

It doesn't show "fancy" bars.

What is actually happening?

Minor enhancement that I think would improve its behaviour. Currently I start the bar if a timer exceeds 300ms, but I always complete it when a state has loaded, but I have to check the .status method to not show it unnecessarily. E.g:

const progressbarTimeouts = []; // can be more than one, in e.g. a redirect
$rootScope.$on('$stateChangeStart', () => {
  progressbarTimeouts.push($timeo

🚀 Feature request

Problem description

Describe what you'd like to be able to accomplish. Including a rough sketch or screenshot can be helpful.

Suggested solution (optional)

Suggest a solution that would solve the problem you have. For example, this may involve adding a new prop, changing an existing prop, or adding a new exported component.

Can we do the following:

if ( progress -> 100)
          print "success"
else
          print "error"

It would be nice to include some documentation for the MultiProgressViewDataSource protocol.

Is your feature request related to a problem? Please describe.
This will be very helpful for those new to this library such that they do not need to comb through the example code provided.

Describe the solution you'd like
It would be great if the documentation can be formatted with Swift

Implement MoveBufferArea in Unix to enable using more cross platform support.

Currently .NET console (of all things) is not properly implemented in .NET Standard 2.1.

If you look here : https://github.com/dotnet/corefx/blob/master/src/System.Console/src/System/ConsolePal.Unix.cs
and search for PlatformNotSupportedException you'll see there are 17 console methods and props that throw th

Hi ! i would like to know if its possible to go beyond 100%

I'm working with some "goal x result" app and it may be possible to go beyond 100% like:

Goal - 1500 steps
Steps - 1900 steps
% - 126%

Using the pattern in the examples on the website, MultiBar::listen will likely hang if an error occurs as the ProgressBar::finish function will never get called. It'd be nice if listen would stop blocking if there aren't any more progress bars.