Server enable / disable
Posted: Sat May 06, 2017 3:56 pm
I'm having trouble enabling and disabling servers
If I am downloading something, then go to the 'servers' tab on the bottom of the screen and disable an active server by clicking on the icon just in front of the server name (it's a green padlock with ssl servers or a blue check with non-ssl servers), the icon turns red and in the 'active/disable' column it says 'disabled'. But nothing seems to happen, the download continues as if nothing happened. Even If I disable all my servers the download still continues.
If I then go to the menubar and choose 'Options' > 'Servers...' , the deactivated servers also show deactivated status there. If I close that window by clicking 'OK', the download suddenly stops but only after I clicked on a server first, just opening the window and clicking 'OK' seems to do nothing. Enabling servers is the same process, just the other way around.
Something funny going on or is there something I don't understand?
Version 6.73 build 4821 on Windows 10 Pro 1703 (the 'creators' update). I think this behaviour was already present before the update to 1703.
If I am downloading something, then go to the 'servers' tab on the bottom of the screen and disable an active server by clicking on the icon just in front of the server name (it's a green padlock with ssl servers or a blue check with non-ssl servers), the icon turns red and in the 'active/disable' column it says 'disabled'. But nothing seems to happen, the download continues as if nothing happened. Even If I disable all my servers the download still continues.
If I then go to the menubar and choose 'Options' > 'Servers...' , the deactivated servers also show deactivated status there. If I close that window by clicking 'OK', the download suddenly stops but only after I clicked on a server first, just opening the window and clicking 'OK' seems to do nothing. Enabling servers is the same process, just the other way around.
Something funny going on or is there something I don't understand?
Version 6.73 build 4821 on Windows 10 Pro 1703 (the 'creators' update). I think this behaviour was already present before the update to 1703.