If I remember correctly, I fixed it by simple adding "upLimit == 0" into condition at the beginning of write() function (and similary downLimit in read()), but it is "upTokens == -1" in DC++.
StrongDC++'s upLimit and also DC++'s upTokens is set once a second. The difference is that I use upLimit also for getting current upload speed limit in write(), but DC++ always uses actual value from SettingsManager. The result is that setting upload speed limit to 0 B/s does not reflect actual value of upTokens (because it can be one second old). I hope it is understandable. -- Limiter bug in DC++ 0.762 / 0.770 https://bugs.launchpad.net/bugs/604983 You received this bug notification because you are a member of Dcplusplus-team, which is subscribed to DC++. Status in DC++: Confirmed Bug description: In dc++ 0.762 and 0.770 I have a recurring bug with using the chat command (/download xx) and changing my download speed while having a download running, by doing this DC++ will reset my currently running downloads my operating system is Windows XP SP3 and as said this has been recreated on 0.770 (originally occured in 0.762 (im guessing this bug has been present ever since the limiter code was introduced) _______________________________________________ Mailing list: https://launchpad.net/~linuxdcpp-team Post to : linuxdcpp-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~linuxdcpp-team More help : https://help.launchpad.net/ListHelp
