Opened 12 years ago

Last modified 8 years ago

#852 new enhancement

Status Change has no effect on accounts that don't support the new Status Type.

Reported by: hdima Owned by: seanegan
Milestone: Component: winpidgin (gtk)
Version: 2.0 Keywords: status change
Cc:

Description

I use Pidgin 2.0.0 on Windows XP. On my system the bug can be shown as follows:

  1. The client in Invisible state. I add IRC account (Accounts->Add/Edit?).
  2. I add some IRC channel (Buddies->Add Chat). Now all working fine and the chat is visible on the buddy list.
  3. I switch the client to Offline state and then back to Invisible state. Now I can't see the previously added channel on the buddy list and new channels can't be added by Buddies->Add Chat because there is now no any IRC accounts in the Account drop-down list. The IRC account still can be viewed and edited in the Accounts menu but it doesn't change anything. The account can be deleted and added again but then all works the same way as described above.

Change History (14)

comment:1 Changed 12 years ago by lschiere

  • Component changed from pidgin (gtk) to winpidgin (gtk)
  • Owner set to datallah

comment:2 Changed 12 years ago by datallah

  • Keywords status change added; irc removed
  • Summary changed from IRC channels disappear after the client disconnects to Status Change has no effect on accounts that don't support the new Status Type.

The problem is that since there is no "Invisible" state for IRC, the status isn't changing from Offline for that account.

I think that ideally what should happen is that it should "fall back" to the closest status that is supported.

comment:3 Changed 12 years ago by lschiere

  • Milestone set to 2.0.1
  • Owner changed from datallah to seanegan

comment:4 Changed 12 years ago by seanegan

  • Status changed from new to assigned

What status is "close" to invisible? The closest is either Available or Offline.

comment:5 follow-up: Changed 12 years ago by hdima

I think for IRC only Offline state should mean offline and all other states should mean online.

comment:6 in reply to: ↑ 5 Changed 12 years ago by spidey3

Replying to hdima:

I think for IRC only Offline state should mean offline and all other states should mean online.

Can't this be acheived already by using a Saved Status where all accounts are Invisible except for the IRC account, which would be set to whichever state you wish to use as "IRC Invisible"?

comment:7 follow-up: Changed 12 years ago by spidey3

Ah, wait, I see the problem now:

  • If you go from Available to Invisible, then IRC stays Available.
  • If you go from Offline to Invisible, then IRC stays Offline.

This is assymetric and confusing. Invisible should be configurable to mean something specific for each of the protocols which do not support it.

comment:8 in reply to: ↑ 7 Changed 12 years ago by hdima

Replying to spidey3:

Ah, wait, I see the problem now:

  • If you go from Available to Invisible, then IRC stays Available.
  • If you go from Offline to Invisible, then IRC stays Offline.

Exactly.

This is assymetric and confusing. Invisible should be configurable to mean something specific for each of the protocols which do not support it.

BTW, something similar should be for other states (like Away, Occupied, etc.) too.

comment:9 Changed 12 years ago by seanegan

  • Milestone changed from 2.0.1 to 2.1.0
  • Type changed from defect to enhancement

I cannot imagine a way to handle this well that does not required added API, so I'm retargetting this for 2.1.0

comment:10 Changed 12 years ago by olleg

With jabber accounts the same. Of cause, I want to set jabber online, when in ICQ I invisible.

Workaround is adding customized saved status where you will able set exactly status for each transport protocols.

IMHO protocols without invisible status must switch to online when common status in invisible. Or, if this is matter of discussion then, allow users configure default statuses in the same manner as we can configure "saved status".

comment:11 Changed 12 years ago by seanegan

  • Milestone changed from 2.1.0 to 2.2.0

this will not be addressed for 2.1.0

comment:12 Changed 11 years ago by kriknav

This issue affects many protocols, like AIM which seems to only support Online, Offline, and Away. What I think is the best solution is to arrange the Statuses in a hierarchical arrangement, that way when a status is set and a protocol doesn't support it, it will set the status to the highest level that it supports.

So if the hierarchy is Offline, Online, Away, Ext. Away, DND, and Invisible, if I select invisible and the protocol only supports as high as Away, it will set my away for that protocol. This will also require research and functions to check if a particular status is supported by a protocol.

Hope this helps.

comment:13 Changed 8 years ago by datallah

Ticket #13732 has been marked as a duplicate of this ticket.

comment:14 Changed 8 years ago by drexen

Perhaps the option of saving different statuses for different protocols?

Note: See TracTickets for help on using tickets.
All information, including names and email addresses, entered onto this website or sent to mailing lists affiliated with this website will be public. Do not post confidential information, especially passwords!