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 481073 - allow "visibility-notify-event" signal to work when composited
allow "visibility-notify-event" signal to work when composited
Status: RESOLVED FIXED
Product: gtk+
Classification: Platform
Component: Widget: Other
2.12.x
Other Linux
: Normal normal
: ---
Assigned To: gtk-bugs
gtk-bugs
Depends on:
Blocks:
 
 
Reported: 2007-09-27 19:46 UTC by William Jon McCann
Modified: 2014-03-05 23:16 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Deprecate GdkEventVisibility and ::visibility-notify-event (2.48 KB, patch)
2014-03-03 23:33 UTC, Matthias Clasen
accepted-commit_now Details | Review

Description William Jon McCann 2007-09-27 19:46:53 UTC
It seems like the "visibility-notify-event" signal doesn't work when the the window is composited.  Might be nice if we can find a way to make it work.  Have the CM set a property or something.

http://library.gnome.org/devel/gtk/unstable/GtkWidget.html#GtkWidget-visibility-notify-event
Comment 1 Benjamin Otte (Company) 2014-02-21 02:25:29 UTC
I think it's preferable to deprecate this event and mention in the docs that it most likely won't work. It's essentially impossible to support with transparency and nobody has cared about this in almost 7 years.
Comment 2 Matthias Clasen 2014-03-03 23:33:00 UTC
Created attachment 270856 [details] [review]
Deprecate GdkEventVisibility and ::visibility-notify-event

These don't really work anymore in a composited world.
Lets make it official.
Comment 3 Benjamin Otte (Company) 2014-03-03 23:39:10 UTC
Comment on attachment 270856 [details] [review]
Deprecate GdkEventVisibility and ::visibility-notify-event

I think I'd get rid of the "more or less". It adds confusion and "it's impossible to track reliably" is clear enough in that yes, the event is still emitted, but it doesn't do what you want it to.