Version: (using KDE KDE 3.5.3) Installed from: Gentoo Packages There should be a global away state for KDE. what could use it : - IM softs (kopete, koversation, ...) on a per application basis (i.e. on kopete, I can choose "use global away state" or something specific to it) - music apps (Amarok pauses when state is set to "sleeping") - screensaver (screensaver activated when state is set to "away1", energy saving state when "away2", etc ...) - kde sound model (no sounds when away for example) - ... what could change it : - time not using computer (just as screensaver today) - unawaying should be proposed by a popup when you use your computer after some time (you're currently away because "away reason" {come back} {keep being away}) - a docklet to set your away state by hand - some applications (state changed to "watching a movie" when ... watching a movie in kaffeine) - a timer (change my state from sleeping to awakenig at 1 p.m.) away states should be configurable enouth so that it is possible to change state but some parts of the state don't change. i.e. when the state change from sleeping to awakenig, IM still display "away : sleeping" because I don't like to speek so early in the morning but Amarok starts playing music ...
Btw, I might be interested to help coding that if enough people think it's interesting and if it has a chance to be accepted. But this would be my first KDE coding (while neither first C++ nor first Qt) and I don't think I could do it in a KDEish way without help.
*** This bug has been confirmed by popular vote. ***
I don't know for dcop, but it seems that dbus is able to broadcast messages. From there, every application that needs to have some kind of "away" state could be listening to this kind of messages. Perhaps something like this could be made standard in kde 4 ?
I won't be working on that until the first of July. Will try to contact some people who work on kopete to know what they think of it. Might also be interesting to see if there is anything like that done in another desktop.
*** This bug has been marked as a duplicate of 122375 ***