Version: (using KDE 4.1.1) OS: Linux Installed from: Gentoo Packages I'd like kopete to respect/keep the status message I set, even with auto away. Presently there's only 3 options (or at least that's what I see): 1) Use a static away message 2) Use "last status message" (almost as static as 1) 3) Don't use auto away, set status manually or ignore the status. What I'd like is to have the auto away to have a third behaviour: Change status to "away", but keep the current status message. And when the "auto-back" is checked (the "become avail..." check box) the status message is kept, only the status returnes to "online" (or maybe better yet to the previous status before the auto away). example scenario where this is desired: status is "I'm home", now I'm online, then I go to the kitchen to make some coffee, etc. Time passes, auto away kicks in. I'm still home so my status message is still what I want, but as I'm not at the computer I want to have 'away' status untill I return to the computer, when it should turn to 'online' automagically. Also, what I'd like is the "good old way" to change status _and_ the staus message at the same time directly via the status menu (but perhaps that's another whish-bug)
Created attachment 27444 [details] A "mockup" of how the config could look hmm... a quick look at the .ui file in qt designed revealed that it apparently is possible to easily make that entire option checkable. A text change + check box and it looks sort of what I'm thinkning of (ui-wise). I have no idea how much coding it'd be behind the scenes (I have no familiarity with the kopete code) to actually make it work though.
Bump still not satisfactory in 4.3.0. Perhaps I wasn't clear on the whish/bug, so let me rephrase: There's still no way to have auto-away _just_ change the _status_ from Online -> Away. (without clobbering current status message)
I've just given Kopete another chance, but having to reset my status message every time I am automatically made "away" may just drive me mad and drive me back to Pidgin again :-p
*** This bug has been confirmed by popular vote. ***