This change adds four new properties to touch events:
* major: diameter of the touch ellipse along the major axis
* minor: diameter perpendicular to major axis
* pressure: a pressure value mapped into the range [0, 1]
* orientation: the angle between major and the x axis [0, 360]
Those values are
Hi,
This version contains several rewordings and documentation additions from Peter
that I missed in the last update, within the first patch of the series, while
the second patch contains no changes compared to v8.
regards
Andreas
Andreas Pokorny (2):
libinput: add orientation and size of touc
event-gui draws the touch contact as two concentric ellipses that indicate
contact pressure through oppacity.
Signed-off-by: Andreas Pokorny
---
tools/event-debug.c | 29 -
tools/event-gui.c | 38 +-
2 files changed, 61 insertions
On Thu, Nov 12, 2015 at 02:20:01PM +0200, Pekka Paalanen wrote:
> On Thu, 12 Nov 2015 11:59:17 +
> Damien Lespiau wrote:
>
> > On Wed, Nov 11, 2015 at 02:01:38PM +0200, Pekka Paalanen wrote:
> > > On Tue, 10 Nov 2015 11:35:35 +
> > > Damien Lespiau wrote:
> > >
> > > > Something else I
On Mon, Nov 02, 2015 at 04:56:13PM +0100, Andreas Pokorny wrote:
> This change adds four new properties to touch events:
> * major: diameter of the touch ellipse along the major axis
> * minor: diameter perpendicular to major axis
> * pressure: a pressure value mapped into the range [0, 1]
> * orie
On Thu, Nov 12, 2015 at 09:38:48AM +, Ucan, Emre (ADITG/SW1) wrote:
> Hi,
>
> I personally create the patches with git format-patch and then copy to the
> email.
> Because I have to use windows and outlook for my company email.
This might be more trouble than worth for you, but for a while I
On Wed, Nov 11, 2015 at 12:32:24AM +0100, Carlos Garnacho wrote:
> Hey,
>
> On Tue, Nov 10, 2015 at 10:47 PM, Peter Hutterer
> wrote:
> > On Fri, Nov 06, 2015 at 09:26:47AM +0800, Jonas Ådahl wrote:
> >> On Thu, Nov 05, 2015 at 12:21:29PM -0600, Derek Foreman wrote:
> >> > On 04/11/15 07:24 PM, J
From: Jason Ekstrand
This provides a standardized mechanism for tracking protocol object
versions in client code. The wl_display object is created with version 1.
Every time an object is created from within wl_registry_bind, it gets the
bound version. Every other time an object is created, it s
On 12/11/15 01:27 PM, Jason Ekstrand wrote:
> Thanks for picking this up! Also, thanks for posting this on the bug,
> I would have missed it otherwise!
Thanks to Pekka for prodding me to do so. :)
> On Thu, Nov 12, 2015 at 11:16 AM, Derek Foreman
> wrote:
>> On 09/11/15 09:06 AM, Pekka Paalane
Thanks for picking this up! Also, thanks for posting this on the bug,
I would have missed it otherwise!
On Thu, Nov 12, 2015 at 11:16 AM, Derek Foreman wrote:
> On 09/11/15 09:06 AM, Pekka Paalanen wrote:
>> On Fri, 6 Nov 2015 12:55:19 -0600
>> Derek Foreman wrote:
>>
>>> wl_surface.damage use
There seems to be some heated debate about whether we should deprecate
the old request or not, and how aggressively we should push people
towards the new one.
I've stayed out of that conversation, and think if we want to consider
that we can still do so after we land the new buffer_damage (now to
On 09/11/15 09:06 AM, Pekka Paalanen wrote:
> On Fri, 6 Nov 2015 12:55:19 -0600
> Derek Foreman wrote:
>
>> wl_surface.damage uses surface local co-ordinates.
>>
>> Buffer scale and buffer transforms came along, and EGL surfaces
>> have no understanding of them.
>>
>> Theoretically, clients pass
On 10/11/15 09:40 AM, Chris Michael wrote:
> mmap() function expects to be passed a void pointer as the address
> here. In order for the kernel to choose a proper address, we should be
> passing NULL instead of 0
Don't like this text because I think it accidentally implies the kernel
will choose a
On Thu, Nov 12, 2015 at 02:20:01PM +0200, Pekka Paalanen wrote:
> IMHO, it is less of a burden to prune accidental patches from Patchwork
> than cause people grief by rejecting legitimate patches. Or does that
> screw up the patch revision or series tracking?
That should work, if not, it's probabl
The leave events in the respective device interfaces has been further
documented so those can convey the necessary info when input is being
redirected out of their currently focused surface.
Only wl_touch is missing something semantically similar, a wl_touch.leave
event has been added so the touch
Hey there,
I think it is worth to bring back some discussion on the client-side
behavior during compositor grabs which I started a few months ago, for
reference the thread started at:
http://lists.freedesktop.org/archives/wayland-devel/2015-April/021407.html
And the first patch sent was:
http://l
On Thu, 12 Nov 2015 11:59:17 +
Damien Lespiau wrote:
> On Wed, Nov 11, 2015 at 02:01:38PM +0200, Pekka Paalanen wrote:
> > On Tue, 10 Nov 2015 11:35:35 +
> > Damien Lespiau wrote:
> >
> > > Something else I noticed on this thead:
> > >
> > > In the reply 20151019013047.GA8175@jelly.loc
On Wed, Nov 11, 2015 at 02:01:38PM +0200, Pekka Paalanen wrote:
> On Tue, 10 Nov 2015 11:35:35 +
> Damien Lespiau wrote:
>
> > Something else I noticed on this thead:
> >
> > In the reply 20151019013047.GA8175@jelly.local from Peter, there's a
> > diff put there for reference, picked up as a
Hi,
I personally create the patches with git format-patch and then copy to the
email.
Because I have to use windows and outlook for my company email.
Best regards
Emre Ucan
Software Group I (ADITG/SW1)
Tel. +49 5121 49 6937
> -Original Message-
> From: wayland-devel [mailto:wayland-de
19 matches
Mail list logo
