kotet / progress Goto Github PK

There is a bug that prevents Bars to calculate their own width when they include non-ascii fill characters (because the length is then greater than the visual length). This makes the bar extend to the next line ("overflow") when the terminal width is to small.

https://dlang.org/spec/ddoc.html

I can't understand why it's not appears. It's present in code and test function that I added is printing.

Here is my code http://vpaste.net/sBR06

I am doing processing of 400k values. Without progress bar I am getting result in 5 seconds. With it it's growing to max value, but it's growing much more slowly than without it?

Could it be reason of slow-down? How can I fix it?

See screenshot.
It's very strange that values are not same. Do you have any ideas why it can be wrong?

When using

auto b = new IncrementalBar();
b.bar_prefix = " [";
b.bar_suffix = "] ";
b.width = 50;
b.max = 500;
foreach(i; 0 .. b.max)
{
  b.next();
}

exception appears:

[█████████████......................................] 129/500
core.exception.RangeError@../../.dub/packages/progress-3.0.0/progress/source/progress/bar.d(97): Range violation
----------------
??:? _d_arraybounds [0x4a4fdd]
??:? progress.bar.__array [0x49e659]
../../.dub/packages/progress-3.0.0/progress/source/progress/bar.d:97 void progress.bar.IncrementalBar.update() [0x49c3e5]
../../.dub/packages/progress-3.0.0/progress/source/progress/package.d:106 void progress.Infinite.next(ulong) [0x49d1aa]
progressbar.d:43 _Dmain [0x49ba72]
??:? _D2rt6dmain211_d_run_mainUiPPaPUAAaZiZ6runAllMFZ9__lambda1MFZv [0x4a818b]
??:? void rt.dmain2._d_run_main(int, char**, extern (C) int function(char[][])*).tryExec(scope void delegate()) [0x4a80b3]
??:? void rt.dmain2._d_run_main(int, char**, extern (C) int function(char[][])*).runAll() [0x4a8130]
??:? void rt.dmain2._d_run_main(int, char**, extern (C) int function(char[][])*).tryExec(scope void delegate()) [0x4a80b3]
??:? _d_run_main [0x4a801f]
??:? main [0x49c031]
??:? __libc_start_main [0xe71f482f]

Adding if (phase >= nphases) phase = nphases - 1; would fix that.

Here is my code http://vpaste.net/5k7PP

I will try to provide the better example...

Perhaps I'm just missing something but calling spinner_.finish(); the output of the spinner is still displayed with the message/last tick. Is there a way to clear this?
Example:

Loading
source-keephdalive-locations.lst => 79%
source-keephdalive-writer.lst No Coverage!

Coverage over 2 files: 39%

I want the Loading \ line cleared so it does not appear in subsequent output.
Other than that this is a great module! Thanks!