Version: (using KDE Devel) Installed from: Compiled sources OS: Linux When MSN or Jabber lose connection, they put a nasty popup window on my screen that won't allow anything else to show up or allow me to use Kopete at all until I hunt it down behind windows and across desktops and click OK (even though the messages are purely informational and not very important). When AIM/ICQ lose connection, there is no notification. Gadu and IRC seem to have no notification. Yahoo doesn't have notification, but then, it never realizes that it's not connected...so it's kind of a moot point there. There should be one setting in knotify, "Account loses connection", and the behaviour specifiable there. I would personally want a passive popup and a sound.
we should probably fix the protocols themselves before worrying about how it's displayed (and we can't really do anything with it during string freeze anyhow, but it's nice to have around)
I'd say we need to auto-reconnect for a couple of times (3?) instead and only do this when that fails. I also tend to lean towards hardcoding the message box if the reconnect fails, as it's a more grave issue than just losing connection by then. Last, I think a KNotify event when reconnecting might be a nice add-on, but independent of the above. Martijn
Subject: Re: [Kopete-devel] Contacts should have "Unknown" status when status is unknown as opposed to offline Martijn Klingens (Tuesday 23 December 2003 14:20) > In reply to your other comment: > > It wouldn't have to be 100% hardcoded would it? > > Surely not. I meant hardcoding the use of a message box over KNotify, not > hardcoding the actual message :) Certainly I agree. IMHO, anything that is currently a popup or sound effect of *ANY* form in Kopete needs to be put in KNotify so that it's easily configurable. It will end a lot of frustrations. But this is a response to the *other* bug, so I'm CCing it to the right place (my fault, I accidentally pasted the wrong To address in before...I think I was much better off when I was just using the links to get to bugzilla instead of trying to use kmail as a bugzilla management tool :-P).
This is a libkopete issue in that first libkopete needs to have 'lost connection' notification before we can add anything else.
which it will have as soon as I implement the new disconnect API for it. :) (See developer.kde.org/development-versions/kde-3.3-features.html)
*** Bug 67287 has been marked as a duplicate of this bug. ***
ok, the new API is implemented (has been for some time) and OSCAR supports it. Support for a few other protocols should be implemented before I close this one.
*** Bug 83267 has been marked as a duplicate of this bug. ***
let open a report for each protocol which doesn't implements it yet