Bug #1537
'Disconnect from Core' is not active during early 'connected' stage
Status:
New
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Start date:
10/16/2019
Due date:
% Done:
0%
Estimated time:
Version:
0.13.0
OS:
Any
Description
I'm having some networking trouble that makes connecting take awfully long time. I've noticed that while Quassel already claims to be 'Connected to ...', then 'Synchronizing', 'Logging in', etc. and basically until the windows appear, the 'Disconnect' option is not yet active and 'Connect' is available (though I don't think it actually works).
I think 'Disconnect' should be available as soon as connecting starts, and should abort any half-connected state that might be happening at the moment.
This is with 0.13.1 (I don't see it in 'Version' field).