summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorSjoerd Simons <sjoerd.simons@collabora.co.uk>2009-05-27 14:05:45 +0100
committerSjoerd Simons <sjoerd.simons@collabora.co.uk>2009-05-27 14:11:56 +0100
commit6cda49f79b43a8a71e66d3e289f856af5fde6761 (patch)
tree32b8eada1f530aeea9bcaf4079f2a4e52f7475e7
parentb587198bba5707fd028c2766be3aff84e3fb74f7 (diff)
downloadtelepathy-mission-control-mission-control-4.tar.gz
Don't close channels on disposemission-control-4
There are various reasons why MCDChannels are disposed, on the current desktop this is either when a client calls close on the telepathy channel directly or when disconnecting from a connection. In the first case calling Close makes no sense (somebody already did this), in the second case it causes troubles when Close has an extra protocol level meaning. For example when using an IRC proxy, closing a the group text means parting the channel on irc, this means on disconnect your proxy will no longer be part of the cahnnel. Which is exactly what you didn't want :)
-rw-r--r--src/mcd-channel.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/src/mcd-channel.c b/src/mcd-channel.c
index 6c198194..d18a057e 100644
--- a/src/mcd-channel.c
+++ b/src/mcd-channel.c
@@ -637,7 +637,7 @@ _mcd_channel_dispose (GObject * object)
return;
priv->is_disposed = TRUE;
- _mcd_channel_release_tp_channel (MCD_CHANNEL (object), TRUE);
+ _mcd_channel_release_tp_channel (MCD_CHANNEL (object), FALSE);
G_OBJECT_CLASS (mcd_channel_parent_class)->dispose (object);
}