Bug 194592

Summary: Return on activity should not return from manually set away status
Product: [Applications] konversation Reporter: Christian (Fuchs) <kde>
Component: generalAssignee: Travis McHenry <wordsizzle>
Status: CONFIRMED ---    
Severity: wishlist CC: hein, wordsizzle
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: Gentoo Packages   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Christian (Fuchs) 2009-05-29 22:02:05 UTC 
Version:           1.2alpha2+ (svn)  (using KDE 4.2.3)
Compiler:          gcc 
OS:                Linux
Installed from:    Gentoo Packages

There is a setting in the identity to automatically set away status after a given time without user activity. There is an option to return from the away status on user activity. 

In my opinion, this should not affect manually set away status. If I set myself as away via /away, and afterwards type something, I still want to be away. I can always type /away or use the keyboard shortcut to return from away status. 

Simple example: 

User a needs to go out of office for a short amount of time. He sets himself as /away. He then remembers that he wants to tell a person he is chatting with when he will be back. As soon as he starts typing, the /away status is revoked and set again. 

Even worse example: 

A user wants to be (for whatever reason) marked as away on one network (e.g. IRCNet).  He still is still active in a different network (e.g. FreeNode). He will lose his away status in IRCNet.
Comment 1 Eike Hein 2009-05-29 22:35:52 UTC 
> A user wants to be (for whatever reason) marked as away
> on one network (e.g. IRCNet).  He still is still active
> in a different network (e.g. FreeNode). He will lose his
> away status in IRCNet.

The "activity" in "Auto-return on activity" is system-level activity: mouse movement or the screensaver stopping (see the What's This tooltips of the respective options in the Identity dialog). When activity occurs, all connections currently set away that are using an identity with auto-return enabled issue a request to be set unaway to the server. IOW, while your wish not to auto-return when the away state didn't originate in the auto-away system would fix the perceived problem in that scenario (provided the away state on IRCnet was indeed the result of a manual away request), it has nothing to do with the typing on the other network specifically.