|
Re: The problem of away messages....: msg#00178network.jabber.py-transports
Daniel Henninger wrote: > Actually then we are effectively talking about the same thing. "1" > means your client just informed you itself. 2 means your client AND > pyaim informed you via a message. 2 also could mean that your client > and the other person's jabber client informed you. 3 means all three > send you something. 0 means you don't even know there WAS an away message. Yeah, we're close enough anyway...I read what you describe as "1" being that your (local) client prints the status (away) message in the text area of the window, possibly only after you send a message. This I would find to be annoying (only mildly, in the first case). I would also include in the "0" case any situation where you actually have to take action to view the status message. e.g. mouse over the contact in the roster for a tooltip, look at the roster where the status message is always underneath the username...and even cases where the status message is at the top of the chat window along with the username. -Alex Mauer "hawke"
py-transports mailing list py-transports@xxxxxxxxxxxxxxxxx http://www.modevia.com/cgi-bin/mailman/listinfo/py-transports |
|
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| Previous by Date: | Re: Re: The problem of away messages....: 00178, Daniel Henninger |
|---|---|
| Next by Date: | webreg 0.5 preview: 00178, James Bunton |
| Previous by Thread: | Re: Re: The problem of away messages....i: 00178, Daniel Henninger |
| Next by Thread: | bad config: NoneType object is not callable: 00178, Wendell Turner |
| Indexes: | [Date] [Thread] [Top] [All Lists] |
| News | FAQ | advertise |