Version: (using KDE KDE 3.2.0) Installed from: Compiled From Sources Compiler: gcc 3.2 OS: Linux When I'm invisible with MSN, I'm 'AWAY' and ICQ shows me even 'ONLINE' while invisible.
for icq that's normal because invisible is an additional flag on top of your normal status. you can be away + invisible online + invisible occupied + invisible etc. The problem with invisible is that if this status is assumed as "offline" then you won't be able to send messages. Maybe KopeteOnlineStatus should get an Invisible status that is a mixture of offline and away (offline to everbody else but away to kopete internally).
This will require that libkopete knows about Invisibility to fix, as Stefan says. It may take a while to fix
ok, MSN and Y! are shown correctly in the Web presence plugin. However, ICQ will take some more work. :/
and gadu and jabber work now, but still not ICQ. I'll have to change how invisible is implemented. (Will: I reassigned to myself since I'm going to have to fix ICQ)
CVS commit by mattr: Add an Invisible status to KopeteOnlineStatus so that MSN, Yahoo, and any other protocols that support being invisible will show as offline in the web presence plugins. ICQ doesn't work yet, but I might be able to take care of that within the next few days. Kopete Developers: I didn't change Jabber or Gadu for this yet. I will get to it, but feel free to leap frog me if I don't do it in a timely manner :-) CCMAIL: 76230@bugs.kde.org CCMAIL: kopete-devel@kde.org M +1 -0 kopete/kimifaceimpl.cpp 1.13 M +3 -1 libkopete/kopeteonlinestatus.cpp 1.32 M +8 -2 libkopete/kopeteonlinestatus.h 1.24 M +1 -0 plugins/webpresence/webpresenceplugin.cpp 1.46 M +1 -1 protocols/msn/msnprotocol.cpp 1.262 M +1 -1 protocols/yahoo/yahooprotocol.cpp 1.74
This commit breaks MSN invisibility in the following way: the auto-away feature continues to do its job even if you are invisible! That is: go invisible, be inactive for 5min (or whatever the time for being marked auto-away is): you are now away, and you have become "visible" without having manually marked yourself as so. That, of course, shoudn't happen.
Then that would be a bug that with MSN. Please file a seperate bug for that one.
Well, you changed this line from ::Away to ::Invisible. The comment states that ::Away is needed. I can't say but that your commit broke the MSN plugin. HDN( KopeteOnlineStatus::Away, 3, this, 8, "msn_invisible", i18n( "Set &Invisible" ), i18n( "Invisible" ) ), //We use away because we don't want to see this state changed when autoaway. I'd suggest (from my ignorance, of course) to revert the change in msnprotocol.cpp and coordinate with the MSN plugin maintainer on how to fix this bug. (Perhaps this has already been done and the agreement was on "Fix #76230 and we'll fix the MSN invisibility issue when sbd. complains". If that's the case, I'll happily report the issue in a separate bugreport.)
Yup, I changed that line. There needs to be a seperate bug filed for the auto-away issue.
I don't think it's a problem with MSN as the auto-away feature simply requests the protocol to set the away status. The protocol can't distinguish whether this is an automatic thing and invisible shouldn't be changed or if it's a user who tries to go away from his invisible status.
from what I understand of the way the away feature works, the bug is in MSN because of the way the weights are arranged. /me shrugs.
The Yahoo! plugin is broken in the same way. IMHO it would be good if the issue was resolved globally, I mean, as a result of discussion between all developers affected and not locally in each plugin. Again from my ignorance, now that ::Invisible exists globally, the auto-away plugin could check if the user is Invisible and do not trigger in that case. I'll file a bug report later, or some other day, explaining it all.
I bet it's the same with Jabber and I think that the problem needs to be solved in the auto-away plugin.
OK, I've reported the bug against the auto-away plugin (bug#84019), I also think that's the right place to fix the issue. Note that there was a lengthy discussion about it last year, which is stored in bug#62427.
Thank you for the bug report. As this report hasn't seen any changes in 5 years or more, we ask if you can please confirm that the issue still persists. If this bug is no longer persisting or relevant please change the status to resolved.