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
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 pen with `libinput_event
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
On Thu, 10 May 2018 12:53:49 +0800
zou lan wrote:
> Hi pekka
>
> I test presentation on my side. The presentation results is not accurate
> because our pageflip event send last frame's timestamp every time. So
> weston_output_finish_frame send last frame's present tine
> to current frame's feedb
On Thu, 10 May 2018 10:10:10 +0200
Markus Ongyerth wrote:
> For the reasons stated above, I think we would be better suited with an
> interface defined as wayland extension. The downside is, that it has to be
> proxied and implemented by the compositor, but I think the advantages
> outweigh
>
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
