After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 655202 - Behaviour when opening chat windows for Meta-Contacts could be improved
Behaviour when opening chat windows for Meta-Contacts could be improved
Status: RESOLVED DUPLICATE of bug 631215
Product: empathy
Classification: Core
Component: Meta Contacts
unspecified
Other Linux
: Normal enhancement
: ---
Assigned To: empathy-maint
Depends on:
Blocks:
 
 
Reported: 2011-07-24 12:20 UTC by Markus Kreusch
Modified: 2011-07-24 13:10 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Markus Kreusch 2011-07-24 12:20:36 UTC
Version: 2.34 (Ubuntu)

When double-clicking on a Meta-Contact a chat window is opened. This window always belongs to the same protocol and there is no way to specify which protocol is used by default.

This is a bit annoying because i want to chat via ICQ most of the time but via double click I always get a googlechat window (unless the contact is only online in ICQ). So I have to select ICQ from the context menu. Another problem is that a new googlechat is opened even if there is already an open ICQ chat window for this Meta-Contact.

In my opinion there are three possilities to enhance this:

* allow to define a user sepcific or overall default protocol or a priority of protocols
* if a chat window is already opened don't open a new one but show the existing one
* if a chat window has been opened and was closed recently, reopen a chat window with that protocol. its annoying for contacts if messages arrive via different protocols in short intervals.

In addition a chat window does not show the protocol it is using. Would be nice if this could be displayed too.
Comment 1 Philip Withnall 2011-07-24 13:10:16 UTC
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.

*** This bug has been marked as a duplicate of bug 631215 ***