Pekka Paalanen wrote:
> Jan Bruns <c...@abnuto.de> wrote:
>
>> Ok. I now have an even earlier point of missing knowledge than I
expected:
>>
>> Why does the generated version of wayland-client-protocol.h reference a
>> server object called "wl_registry_interface"?
>
> These interface structures are used both server and client side. The
> core of libwayland needs to know the message signatures for it to be
> able to marshall them. As we want people to be able to use
> new extensions (XML files) without needing to rebuild libwayland to
> match, the signatures must be provided to libwayland.
I see. Probably an implementation detail a beginner like me shouldn't
focus on too much.
I've just stumbled upon a more serious question:
registry.bind() doesn't have a version parameter, and also
wl_proxy_add_listener().
Doesn't this mean that an App that doesn't know the latest version of an
interface cannot use libwayland anymore?
How to tell libwayland to not attempt to call nonexisting callbacks?
Gruss
Jan Bruns
_______________________________________________
wayland-devel mailing list
wayland-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/wayland-devel
