[pygobject] fix GtkBuilder signal connection 'after' logic
- From: Ryan Lortie <ryanl src gnome org>
- To: commits-list gnome org
- Cc:
- Subject: [pygobject] fix GtkBuilder signal connection 'after' logic
- Date: Wed, 8 Feb 2012 21:35:33 +0000 (UTC)
commit 671f9b0dd73ac41a84caf9d1f04cec351bc01b47
Author: Ryan Lortie <desrt desrt ca>
Date: Wed Feb 8 16:06:22 2012 -0500
fix GtkBuilder signal connection 'after' logic
All GtkBuilder signals are presently being connected 'after', ignoring
what is specified in the builder XML. This is due to an obvious logic
error.
https://bugzilla.gnome.org/show_bug.cgi?id=669705
gi/overrides/Gtk.py | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
---
diff --git a/gi/overrides/Gtk.py b/gi/overrides/Gtk.py
index 1d0cb49..2b44282 100644
--- a/gi/overrides/Gtk.py
+++ b/gi/overrides/Gtk.py
@@ -350,7 +350,7 @@ class Builder(Gtk.Builder):
if not _callable(handler):
raise TypeError('Handler %s is not a method or function' % handler_name)
- after = flags or GObject.ConnectFlags.AFTER
+ after = flags & GObject.ConnectFlags.AFTER
if connect_obj is not None:
if after:
gobj.connect_object_after(signal_name, handler, connect_obj)
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]