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 699419 - Provide access to wayland globals
Provide access to wayland globals
Status: RESOLVED WONTFIX
Product: gtk+
Classification: Platform
Component: Backend: Wayland
unspecified
Other Linux
: Low enhancement
: ---
Assigned To: gtk-bugs
gtk-bugs
Depends on:
Blocks:
 
 
Reported: 2013-05-01 20:29 UTC by U. Artie Eoff
Modified: 2013-07-30 12:10 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description U. Artie Eoff 2013-05-01 20:29:05 UTC 
krh's suggestion in bug 699415 is still useful:

krh wrote:
> I think it would make sense for GTK+ to provide access to known globals and
> emit a signal on GdkDisplay when new globals are announced or existing once are
> removed.
Comment 1 Rob Bradford 2013-07-03 14:40:18 UTC 
I'm not sure about this..it's really not much effort to listen for globals on the registry. Is there a particular use case for this in mind?
Comment 2 U. Artie Eoff 2013-07-03 14:49:57 UTC 
(In reply to comment #1)
> I'm not sure about this..it's really not much effort to listen for globals on
> the registry. Is there a particular use case for this in mind?

No.  It's just here based on krh's comment.
Comment 3 Rob Bradford 2013-07-30 12:10:40 UTC 
I don't think we should do it. Listening for globals is the best way.