Version: (using Devel) Installed from: Compiled sources We're getting the same icon for away and busy in the systray icon (while it was not on Kopete3) and I think it would be useful to have it. e.g. the clock for away and the red sign for busy
I confirm this bug. Whenever I set my global status to "Busy" I get a "Away" icon at systray (the small clock, instead of the red circle).
Someone with higher privileges could mark bug #188106 as duplicated for this one.
This problem happens almost everywhere in the application: - Contacts' list - Systray (as reported above) - Bottom-right corner There's no distinction from away and busy status.
SVN commit 1022546 by apol: Let kopete to distinguish between away and busy. BUG: 179080 M +6 -0 kopete/contactlist/contactlistmodel.cpp M +1 -0 kopete/contactlist/kopeteitemdelegate.cpp M +10 -0 kopete/kopetedbusinterface.cpp M +4 -0 kopete/kopetewindow.cpp M +18 -19 kopete/systemtray.cpp M +4 -1 libkopete/kopeteaccount.cpp M +8 -3 libkopete/kopetemetacontact.cpp M +2 -1 libkopete/kopeteonlinestatus.cpp M +7 -3 libkopete/kopeteonlinestatus.h M +12 -7 plugins/statistics/statisticscontact.cpp M +14 -0 plugins/statistics/statisticsdialog.cpp M +5 -1 plugins/webpresence/webpresenceplugin.cpp M +2 -1 protocols/bonjour/bonjouraccount.cpp M +2 -2 protocols/gadu/gaduprotocol.cpp M +1 -1 protocols/groupwise/gwprotocol.cpp M +1 -1 protocols/jabber/jabberprotocol.cpp M +1 -1 protocols/meanwhile/meanwhileprotocol.cpp M +2 -1 protocols/oscar/aim/aimaccount.cpp M +2 -2 protocols/oscar/aim/aimstatusmanager.cpp M +2 -2 protocols/oscar/icq/icqstatusmanager.cpp M +1 -1 protocols/skype/skypeprotocol.cpp M +15 -1 protocols/testbed/testbedaccount.cpp M +4 -0 protocols/testbed/testbedaccount.h M +5 -3 protocols/testbed/testbedprotocol.cpp M +4 -0 protocols/testbed/testbedprotocol.h M +5 -2 protocols/winpopup/wpaccount.cpp M +2 -1 protocols/wlm/wlmaccount.cpp M +2 -2 protocols/wlm/wlmprotocol.cpp M +3 -3 protocols/yahoo/yahooprotocol.cpp WebSVN link: http://websvn.kde.org/?view=rev&revision=1022546
*** Bug 188106 has been marked as a duplicate of this bug. ***