calculating percentage versus calculating time is a 10x harder code implimentation - to throw out percent you just do that, before you start you know you have 107,000 items to handle, increment the % every 107 items. To calculate "time" and have it behave realistically you have to do 1% of the file i/o (call that A), 1% of the memory i/o (call that

and then ballpark the time (100 * [A+B] ) - way to much bloat code for what little it accomplishes (think about this becoming a 3 meg executable just to time estimate correctly. again I'll defend coding this feature and not coding it. Anybody do the "1 hour" windows 95 install on a modern pc - it takes like 13 minutes. or even the ~32 minute win 98se install - it ticks off a minute every 20 seconds. time is a real tough thing to do right. KISS - keep it simple s***** - text field with however many items is appropriate, update it as needed. a smart user looks at his watch, notices it took 3 minutes for the first 10%, then leaves on a soda break for 27 minutes. (and yes, I was cleaning an old dog machine and that first clean removed 501Megs, and took 30 minutes)... unfortunately with the current non-progress bar I had to just look back at it every 10 minutes and wonder if the old dog had froze.
All that said - I still want to give kudos out the coders - this is really the only feature that is poorly implemented, and as far as my other posts in other areas go, you can't dog a coder for not adding a feature, just screwin one up
Thanks programmers and programmets