Version: 0.9.2 (using KDE 3.3.2 Level "a" , unofficial build of SUSE ) Compiler: gcc version 3.3.3 (SuSE Linux) OS: Linux (i686) release 2.6.4-52-default Hi, sometimes my ICQ disconnects due to DSL disconnection after 24 hours (IP-change) or other (maybe unknown) protocol issues. kopete doesn't offer a functionality to reconnect after a disconnection from the server. It would be easy to write a shell script which asks kopete every minute if it is still connected maybe via isConnected( and if not I can use the DCOP connectAll() method again to reconnect to the ICQ system. What do you think? Thanks and nice application anyway Pietz
> sometimes my ICQ disconnects due to DSL disconnection after 24 hours (IP-change) or other (maybe unknown) protocol issues. kopete doesn't offer a functionality to reconnect after a disconnection from the server. It would be easy to write a shell script which asks kopete every minute if it is still connected maybe via isConnected( and if not I can use the DCOP connectAll() method again to reconnect to the ICQ system. It does. Current ICQ implementeation doesn't use it for some reason. There is new ICQ implementation waiting to be merged to HEAD, around 20ish. That should contain reconnect feature.
Hi, > It does. Current ICQ implementeation doesn't use it for some > reason. There is new ICQ implementation waiting to be merged to > HEAD, around 20ish. That should contain reconnect feature. OK, sounds cool but anyway I think that the method isConnected() is still useful when you want to script kopete by yourself with the shell. Just an idea - maybe someone needs it ;) Pietz
The accounts() method returns something like: IRCProtocol||Freenode_2 ICQProtocol||140319753 JabberProtocol||tassilo@amessage.info Perhaps you could modify it so that it returns: IRCProtocol||Freenode_2||online ICQProtocol||140319753||offline JabberProtocol||tassilo@amessage.info||online Regards, Tassilo
I second this request, but not in relation with ICQ, I want to be able to check on remote machines what the status is of an account and execute a script based on the result, thanks!
Not in our dbus interface yet either.
Since auto reconnect seems to work properly we can close this issue.