Re: How fwrd-compatible is using dlopen and core only?

Oh, I solved the problem with the extern variable (wl_registry_interface), I could get a pointer to it using `dlsym(handler, "wl_registry_interface")`. The other question remains: can I use the content of the inline functions directly (to avoid the need to include protocol headers)? Is forward

How fwrd-compatible is using dlopen and core only?

Hi, For the OSS window framework that I'm working on, the Wayland backend requires linking to the libraries. No problem here. I wish to give an option to load the Wayland libraries at runtime, using `dlopen()`. The problem is that some functions are inline'd in the headers or part of the exten

Re: How fwrd-compatible is using dlopen and core only?

Another thing that I realized: Headers, such as `wayland-client-protocol.h`, contains declarations such as `wl_registry_interface`, which is an extern variable. If I am going to copy-paste this: wl_proxy_marshal_constructor((struct wl_proxy *) wl_display, WL_DISPLAY_GET_REGISTRY, &wl_registry_

Re: Release schedule

Any chance of the XDG decoration protocol being part of this release plan? ___ wayland-devel mailing list wayland-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/wayland-devel

Re: How to properly keep track of wl/xdg output?

Oh, the ID is unique for all type of objects! That works :) Thanks, Felipe ‐‐‐ Original Message ‐‐‐ On May 14, 2018 5:38 AM, Pekka Paalanen wrote: > On Sat, 12 May 2018 06:34:36 -0400 > > ferreiradaselva ferreiradase...@protonmail.com wrote: > > > Hi, > >

Re: Proposal: make "hardware_id_wacom" more generic

Hi Peter, I see your point that there would still need to exist vendor-specific code. My point is that reading that vendor-specific data would be responsibility of the end-user (the people making a wayland client), instead of """polluting""" the protocol with vendor-specific details. But, if th

Proposal: make "hardware_id_wacom" more generic

It feels a bit off that a vendor-specific event is exposed to the client. Why not something like: ``` void (*hardware_specific_id)(void *data, struct zwp_tablet_tool_vX *zwp_tablet_tool_vX, uint32_t length, uint8_t *id); ``` The tablet name is already exposed on the event

Re: How to get position of tablet pen relative to surfaces?

Nevermind, I found that there is an unstable protocol for tablets that provides that, so I will try it. ‐‐‐ Original Message ‐‐‐ On May 12, 2018 7:04 PM, ferreiradaselva wrote: > I made a libinput context that I use to get the coordinates of the (wacom) > tablet pe

How to get position of tablet pen relative to surfaces?

I made a libinput context that I use to get the coordinates of the (wacom) tablet pen with `libinput_event_tablet_tool_get_x()` and `libinput_event_tablet_tool_get_y()`. Since libinput knows nothing of surfaces, the value is obviously the global position of the pen. If I had the global position of

How to properly keep track of wl/xdg output?

Hi, Excuse me if this is something that is already explained in the protocols, but I couldn't find the solution by myown. I'm working on a client-side library, and I need to keep track of wl (or xdg in the future) outputs. My first idea was: - Have a `wl_list` in my context - In the global list

Re: Can I copy-paste Wayland generated header in my own library header?

Hi, > Original Message >From: ppaala...@gmail.com >To: ferreiradaselva > > Hi, > > first, IANAL, of course. > > The copyrights header you get in the generated headers and code comes > from the XML files. It is the license of the XML protocol >

Scanner with --no-documentation option (source-code included)

https://gist.github.com/ferreiradaselva/ad04b8c6302a376f4bff0477ea01d129 One problem still is that it uses a global boolean `print_doc`. I don't know in which structure to put that variable that would make acessible everywhere. -- Felipe Ferreira da Silva_

Can I copy-paste Wayland generated header in my own library header?

Good morning. I'm writing a cross-platform window framework, like GLFW, but containing only two files (a source and a header). I would like to copy and paste the content of the xdg-shell.h generated with wayland-scanner into my header (swfw.h), between #ifdef/#endif, so if the user compiles fo

Re: Who generate the headers?

gt; Local Time: December 2, 2017 9:02 AM > UTC Time: December 2, 2017 12:02 PM > From: pkerl...@casix.org > To: wayland-devel@lists.freedesktop.org > ferreiradaselva > > Hi, > > 2017-12-02 (土) の 06:05 -0500 に ferreiradaselva さんは書きました: > >> Hello, everyone >>

Who generate the headers?

Hello, everyone I'm still learning how the distribution to the access of the API works. I'm making a library like GLFW/SDL2 with Wayland as one of the backends. I have in my system `/usr/include` the headers of my interest `wayland-client-protocol.h` and `wayland-client.h`. However, the protoco

Re: [ANNOUNCE] wayland-protocols 1.12

Thank you!!! -- Felipe Ferreira da Silva Sent with [ProtonMail](https://protonmail.com) Secure Email. > Original Message > Subject: [ANNOUNCE] wayland-protocols 1.12 > Local Time: December 1, 2017 11:41 PM > UTC Time: December 2, 2017 2:41 AM > From: jad...@gmail.com > To: wayl

Re: Hide surface

> Subject: Re: Hide surface > Local Time: November 27, 2017 3:48 PM > UTC Time: November 27, 2017 6:48 PM > From: matt.hoos...@gmail.com > To: ferreiradaselva > wayland-devel@lists.freedesktop.org > > On Sun, Nov 26, 2017 at 2:23 PM, ferreiradaselva > ferreiradase.

Hide surface

Hi, My first time posting here (sorry if I'm posting on the wrong place). I'm working on this window creation framework (https://github.com/ferreiradaselva/swfw), and for the Wayland backend I need to implement a function to hide the "window". I found that that is do