verigak
commented
12 years ago Thanks, that's a good idea. I have added a start method in a3fb1b4fccc794e94e0cd26a835289f121bd16c0.
As for the max attribute, I'd rather leave it as is, size could potentially confuse with the size of the progress bar.
Not printing a newly created progress bar gives flexibility, but it would be better if users were given a choice about this. Using goto(0) does not work (unless self.backtrack is turned on) since the library computes a delta to decide whether or not to run the update() method. Even if this worked, it would be a hack. A more proper solution would be to add a show() or even better a start() method for this purpose (you have a finish() one implemented) .
P.S: If I were you I would also rename "max" attribute to "size". It is still monosyllable and it sounds better. I've already asked 2000 chicks about this. Of course this would break the code of millions of users including myself but I have been doing some rough calculations lately and I think I will survive. Even if I don't, please don't cry for me. The planet is overpopulated anyway! :-)