[beast: 8/49] BSE: ignore warnings for remotely disconnected signals that are already disconnected
- From: Tim Janik <timj src gnome org>
- To: commits-list gnome org
- Cc:
- Subject: [beast: 8/49] BSE: ignore warnings for remotely disconnected signals that are already disconnected
- Date: Wed, 1 Jul 2015 11:29:46 +0000 (UTC)
commit 7896444aa46ce5060cd919f75d75a0d2f5666dfd
Author: Tim Janik <timj gnu org>
Date: Mon Jun 22 02:01:28 2015 +0200
BSE: ignore warnings for remotely disconnected signals that are already disconnected
One possible scenario the old behavior could trigger bogus warnings is if
BSE still keeps track of closure and tries to disconnect after they have been
auto-disconnected by g_object_run_dispose.
bse/bseglue.cc | 3 ++-
1 files changed, 2 insertions(+), 1 deletions(-)
---
diff --git a/bse/bseglue.cc b/bse/bseglue.cc
index a6e1d34..ec4a540 100644
--- a/bse/bseglue.cc
+++ b/bse/bseglue.cc
@@ -1026,7 +1026,8 @@ bglue_proxy_request_notify (SfiGlueContext *context,
else
p->closures = slist->next;
g_slist_free_1 (slist);
- g_signal_handler_disconnect (item, bclosure->handler_id);
+ if (g_signal_handler_is_connected (item, bclosure->handler_id))
+ g_signal_handler_disconnect (item, bclosure->handler_id);
g_closure_invalidate (closure);
g_closure_unref (closure);
return FALSE;
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]