ly works. All I know about that is the wayland-1.18.0
makefiles still work with it, and generate libs that seem to work for
precompiled apps, but expect to see lots of C-related fine-tuning tasks
to still remain.
Gruss
Jan Bruns
diff -ru wayland-1.18.0/protocol/wayland.xml p3/protocol/waylan
idn't notice
some notification-sheme about object deletion).
> I think there is nothing more I can give you. Wayland is not what you
> imagined or wished for.
Nobody knows what the future is.
Thanks.
Gruss
Jan Bruns
___
wayland-devel mailing list
wayland-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/wayland-devel
he same implementation. Between
> processes, each process can use a totally different Wayland
> implementation if you want to, as long as they all talk the same binary
> wire format.
Well, isn't that yet still pretty much a sleeping dreamer...
Gruss
Jan Bruns
___
wayland-devel mailing list
wayland-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/wayland-devel
HR, in addition to
the existing VK_STRUCTURE_TYPE_WAYLAND_SURFACE_CREATE_INFO_KHR?
> If someone had the time, our email discussion would be a good
> indication for what to improve in the Wayland documentation.
For my part, I'll probably work through more advance API usage pattern
much relevance,
given specific sets of workflows. That's bad news to me, a
disappointment, because making things easier for the distant future was
my only motivation for focussing on wl a bit.
Gruss
Jan Bruns
___
wayland-devel mailing list
wayland-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/wayland-devel
Jan Bruns wrote:
> 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 l
Pekka Paalanen wrote:
> Jan Bruns 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"?
>
On 09.09.20 17:44, Jan Bruns 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"?
It is (contrary to what me thought, again mixing up
e
typeless testing code made wl_proxy_marshal_constructor return NULL
(instead of crashing). Maybe some detail I have done wrong, but I don't
understand what's going on here anyway.
Gruss
Jan Bruns
___
wayland-devel mailing list
wayland-devel@lists.freedesktop.or
not so common usage of struct/union-keywords within parameter
lists, and the very minmal delta in the excessive comments talking about
that difference on the opposite than expected versions.
I'll have to reevaluate the amount of required work now, and maybe I
could start with simple tests.
" API of libwayland into your
> preferred language, and then write a code generator tool similar to
> wayland-scanner that generates the bindings from XML to your language,
> using your wrapped libwayland calls. You have the freedom to design the
> API produced by your code gene
s a bit difficult to find. It probably gets
auto-generated on installing wayland, a step that I didn't try, since
wayland already was installed here. But I found it in /usr/include.
Could someone please outline how to use the API for the n
12 matches
Mail list logo
