summaryrefslogtreecommitdiff
path: root/progressbar.go
diff options
context:
space:
mode:
authorPietro Gagliardi <[email protected]>2014-06-04 19:09:26 -0400
committerPietro Gagliardi <[email protected]>2014-06-04 19:09:26 -0400
commitfb7e638d697a909ef791b11837ff3c17be933bd3 (patch)
treebcecf49dae85e331ae427e02e14953081f41eb23 /progressbar.go
parentbd08967a5a1a27995f8390d8e2aeb247cdf01347 (diff)
Resolved TODO about indeterminate ProgressBar repetition by deciding to leave it to the implementation.
Diffstat (limited to 'progressbar.go')
-rw-r--r--progressbar.go2
1 files changed, 1 insertions, 1 deletions
diff --git a/progressbar.go b/progressbar.go
index 520fb0c..57f5943 100644
--- a/progressbar.go
+++ b/progressbar.go
@@ -28,7 +28,7 @@ func NewProgressBar() *ProgressBar {
// If percent is in the range [0,100], the progressBar shows that much percent complete.
// If percent is -1, the ProgressBar is made indeterminate.
// Otherwise, SetProgress panics.
-// TODO what happens if you repeatedly call SetProgress(-1)?
+// Calling SetProgress(-1) repeatedly will neither leave indeterminate mode nor stop any animation involved in indeterminate mode indefinitely; any other side-effect of doing so is implementation-defined.
func (p *ProgressBar) SetProgress(percent int) {
p.lock.Lock()
defer p.lock.Unlock()