Ah.. Not saying I like that the scheduler can connect the client as well, but it makes sense I suppose. I was treating the scheduler like it is in most other programs, a set limit for certain times. Like it can stop connections, but it doesn't automatically make them, it just limits them. I now see that this one can control connections as well, so it automatically assumes you want to be connected as long as the scheduler isn't set to otherwise. I think at one point I had the client disconnected and it reconnected itself later (Perhaps at the top of an hour). Since I use my scheduler to simply limit speed throughout the day, it makes sense to me that the scheduler should not control whether or not the client actually connects. Perhaps it should be a future toggle option, whether or not you want the scheduler to connect you. I like mine to just limit speeds, not to dictate when I want my client connected.
Better explanation... If it just limits speed, then you can tell it no bandwidth at certain periods of the day, then just leave it auto connected and it will download when you want it to. The way it appears set up now, the thing automatically assumes you always want to be connected, even when you don't. I don't always want to be connected, but I don't schedule it either. I like to use other clients as well and I don't share connections. Perhaps I am just confused because I haven't seen a scheduler that worked specifically like that. It limits both speed and when it thinks you should download, even when you don't tell it to download.
Either way, I guess who cares. Still glad that the scheduler bug is not just me. That was driving me insane because I sometimes like to open it and not even bother checking anything, so that was causing problems.
