I noticed an amazing bug in the implementation of the ttk progress bar when I was looking into [7e28ef577a].  When the loop incrementing the progress bar reached the end, the progress bar was rapidly redisplayed even though nothing was changing.  (The value at the end of the loop was 99.) It turned out that AnimationEnabled was returning 1 even though the progress bar was determinate.  The cause was a misplaced parenthesis dating back to 2006.

The effect is to make any determinate progress bar be animated almost all of the time. This may explain, at least partly, the reports that progress bars significantly increase CPU usage even when they are not doing anything.

Here is the problematic code:
```
    return pb->progress.period > 0
	&& value > 0.0
	&& (   value < maximum
	    || pb->progress.mode == TTK_PROGRESSBAR_INDETERMINATE);
```

The correct code (with extra parentheses for clarity) would be:
```
    return (pb->progress.period > 0 && value > 0.0 && value < maximum)
	|| (pb->progress.mode == TTK_PROGRESSBAR_INDETERMINATE);
```