[PATCH] automatically connect/disconnect on network status changes (w/ KDE)
With this patch, my quasselclient automatically connects and reconnects depending on Solid's status. So when my network comes up, quasselclient automatically reconnects to the core, so I don't have to do this manually. It's a feature for those linking against KDE.
I've built-tested it without and it seems I didn't do any harm there. If anyone could have a look if the user interaction is still OK for monolithic client/core, that'd be nice.
Actually make the client/core connection settings do something
This introduces ping timeout settings and automatic reconnect. If you're using
KDE, you'll get Solid support to disconnect and reconnect as your network connection
Thanks to sebas for the initial patch for Solid support!
#1 Updated by bbigras over 13 years ago
This feature is a must when used with KDE.
I normally use quasselclient with a core on a server. I tried this patch with the monolithic client and when the Internet connection went back on, "showCoreConnectionDlg(true)" make the monolithic client act like quasselclient, it connected to the core on my server.
I added a check to make it work only with the quasselclient.
For the monolithic client I think it could kill every connection when the Internet connection drop and when it come back on it could reactivate every connection with the "Automatic Reconnect" option activated.
#2 Updated by DeepDiver over 13 years ago
Well a similar feature has bee requested by a debian user as well:
#3 Updated by Sputnick over 13 years ago
- Status changed from New to Assigned
- Assignee set to Sputnick
- Target version set to 0.5.0
- % Done changed from 90 to 50
- Estimated time deleted (
Working on this now. I will probably couple this with a more sensible CoreConnectionDialog and add something for monolithic Quassel (probably a general online/offline mode thing that the various parts of Quassel could react to).
Thanks for the input so far!