The new API returns scroll wheels as fractions of 120.
Signed-off-by: Peter Hutterer
---
Turns out it's not the most complicated patch...
This is an RFC only because libinput hasn't been released yet, and it's
waiting on the kernel release anyway. Given the expected delay, I hope
autotools is re
Pekka Paalanen wrote:
> yes, this is a good concern. I think we might be needing an extension
> to tell the client which output to prioritise for. We already have an
> analogue of that in the Presentation-time extension: a wl_surface's
> timings can only be synchronised to one output at a time,
Hi Simon Ser,
Thanks for your comments.
I am also not sure about whether the protocol belongs here or not, and
that's why I had first proposed the same in weston, along with the
implementation and the client application -
Merge request:
_https://gitlab.freedesktop.org/wayland/weston/merge_reque
Hi,
Thanks for your patch. However, I don't think it belongs to wayland-protocols.
wayland-protocols isn't designed for all common Wayland protocols. For instance,
the IVI shell isn't there, and has a similar use-case (although not limited to
closed systems). Also some other protocols like layer-s
From: Ankit Nautiyal
This patch adds the protocol for providing content-protection to a
client application. The content-protection here refers to the 'on the
wire protection' e.g. HDCP1.4 HDCP2.2.
The client application can request for the content-protection,
specifying the type of the content: T
On Fri, 25 Jan 2019 10:05:47 -0600
Derek Foreman wrote:
> On 1/18/19 4:20 PM, Derek Foreman wrote:
> > Hi all,
> >
> > It's been quite some time since our last weston release, and there's
> > been some discussion of getting the next one out in the January to March
> > timeframe (this would be th
This allows clients to destroy a gesture object before they disconnect.
The request isn't named "destroy", as this would conflict with
wayland-scanner's auto-generated destructor (which just destroys the
client-side object without sending any request).
Signed-off-by: Simon Ser
Reviewed-by: Jonas
On Mon, Jan 28, 2019 at 08:33:55AM +, Simon Ser wrote:
> This allows clients to destroy a gesture object before they disconnect.
>
> The request isn't named "destroy", as this would conflict with
> wayland-scanner's auto-generated destructor (which just destroys the
> client-side object withou
This allows clients to destroy a gesture object before they disconnect.
The request isn't named "destroy", as this would conflict with
wayland-scanner's auto-generated destructor (which just destroys the
client-side object without sending any request).
Signed-off-by: Simon Ser
---
Changes in v2
