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 699415 - Store and allow access to wayland global interfaces
Store and allow access to wayland global interfaces
Status: RESOLVED INVALID
Product: gtk+
Classification: Platform
Component: Backend: Wayland
unspecified
Other Linux
: Normal normal
: ---
Assigned To: gtk-bugs
gtk-bugs
Depends on:
Blocks:
 
 
Reported: 2013-05-01 19:39 UTC by U. Artie Eoff
Modified: 2013-05-01 20:13 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description U. Artie Eoff 2013-05-01 19:39:53 UTC 
Apps should be able to bind to custom wayland interfaces (i.e. a test extension).  Wayland only acknowledges/invokes one registry listener per display connection. Thus, the global interfaces should be cached internally (name, version, id) when they are handled and be API accessible to allow apps to bind them.
Comment 1 Kristian Høgsberg 2013-05-01 19:43:52 UTC 
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.

However, wayland currently does allow for multiple wl_registry proxies in the client.  Get the wl_display from GdkDisplay and call wl_display_get_registry() to create a new registry listener.
Comment 2 U. Artie Eoff 2013-05-01 20:13:09 UTC 
(In reply to comment #1)
> 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.
> 
> However, wayland currently does allow for multiple wl_registry proxies in the
> client.  Get the wl_display from GdkDisplay and call wl_display_get_registry()
> to create a new registry listener.

Hmmm... I tried multiple wl_registry proxies before and I coulda sworn it didn't work.

But, I tried again and voila, it worked! Ugh. Silly me.