|
Notes |
|
|
|
|
This happens because drawing of the progress bars are cached. Main bar for 5s and clientbars for 10s. |
|
|
|
(0000828)
|
|
m2kio
|
|
2005-04-07 15:21
|
|
|
negative. just tested. other peers' bars are not updated on their own. they are only updated on any other event that updates the (entire) list. these may be frequent (probably) if there is much dl activity or user induced (switching tabs, switching apps et.al.). until then they are not updated. |
|
|
|
|
Positive. The progress-bars are cached in the custom-drawing routines, but unless those functions are actually invoked (for instance by the source or list being refreshed), it will just stay as what was last drawn on the list, regardless of the fact that the cached value has gone invalid due to passed time.
The alternative would be to force updates at a set interval (wasteful) or implement a way for the remaining sources to be notified once a chunk has been completed. |
|
|
|
|
|
I'm marking this as "won't fix", as the issue is rather minor, and the solution would be either extremly wasteful or exceedingly complex. |
|