3 ms·
I once worked on making a progress bar for a process that had a known number of tasks. Unfortunately not all tasks would take the same amount of time, and it wa
by thayne 6y ago
I once worked on making a progress bar for a process that had a known number of tasks. Unfortunately not all tasks would take the same amount of time, and it was impossible to know the relative amount of time each task would take beforehand. I did the logical thing, and had the progress bar advance 1/nth every time a task completed, with an animation to make it less jarring. A few weeks later, the product manager came to me and told me I needed to make it so the progress bar kept slowly moving up if no tasks were completed for a certain amount of time, so the user would know that work was still being done. Fine. But what happens if the task takes so long that it goes past the mark for the next completed task? Well, when the task is actually completed, it moves backwards of course.
- knodi123 6y agoI made zeno's progress bar; it always keeps moving, but never quite finishes until you send it a :done: event, at which point it wastes half a second animating the remainder of the progress bar. Never had a single complaint, and no one noticed that it had nothing to do with what was going on under the hood.
- marcosdumay 6y agoLike the current Windows file copy dialog, but using the entire bar instead of the interval between 98% and 100%?