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 346280 - No way to call gdk_window_add_filter(NULL, ...)
No way to call gdk_window_add_filter(NULL, ...)
Status: RESOLVED WONTFIX
Product: pygtk
Classification: Bindings
Component: gdk
unspecified
Other Linux
: Normal normal
: ---
Assigned To: Nobody's working on this now (help wanted and appreciated)
Python bindings maintainers
gnome[unmaintained]
: 512851 (view as bug list)
Depends on: 156948
Blocks:
 
 
Reported: 2006-06-30 11:28 UTC by Björn Lindqvist
Modified: 2018-08-17 13:43 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Björn Lindqvist 2006-06-30 11:28:36 UTC 
gdk.Window has a method named add_filter() which wraps gdk_window_add_filter(). but gtk_window_add_filter() can also be called with its first argument NULL. Writing gdk_window_add_filter(NULL, somefunc, NULL) will set it up so that somefunc listens to all GDK events to all windows. You can't do that with pygtk.

I suggest a utility function: gdk.window_add_filter_all_windows(function, data=None) which wraps gdk_window_add_filter(NULL, function, data).
Comment 1 Johan (not receiving bugmail) Dahlin 2008-01-29 17:50:51 UTC 
*** Bug 512851 has been marked as a duplicate of this bug. ***
Comment 2 André Klapper 2018-08-17 13:43:25 UTC 
pygtk is not under active development anymore and had its last code changes
in 2013. Its codebase has been archived:
https://gitlab.gnome.org/Archive/pygtk/commits/master

PyGObject at https://gitlab.gnome.org/GNOME/pygobject is its successor. See https://pygobject.readthedocs.io/en/latest/guide/porting.html for porting info.

Closing this report as WONTFIX as part of Bugzilla Housekeeping to reflect
reality. Feel free to open a task in GNOME Gitlab if the issue described in this task still applies to a recent version of PyGObject. Thanks!