From: Quentin Glidic
These are useful to implement grabs.
Signed-off-by: Quentin Glidic
Reviewed-by: Jonas Ådahl
Acked-by: Giulio Camuffo
Differential Revision: https://phabricator.freedesktop.org/D1245
---
libweston/compositor.h | 33 +
libweston/input.c | 374 +++
amp; ILM_INPUT_DEVICE_TOUCH))
>> continue;
>> <-
>>
>>
>> Thanks & Regards,
>> Vikash
>>
>> On Mon, Dec 14, 2015 at 3:25 PM, Vikas Patil wrote:
>>
Hi,
On Wed, Jan 6, 2016 at 8:30 AM, Peter Hutterer
wrote:
> CC-ing Andreas this time, forgot about it in my original reply, sorry about
> that.
>
> On Wed, Jan 06, 2016 at 03:35:49PM +0900, 강정현 wrote:
> > In Andreas Pokorny patch, only support part of standard linux MT
> protocols
> > except AB
they be supported ? Do you have any ideas?
you'll need to add them to the kernel first. what types of events are we
talking about here?
Cheers,
Peter
> > -Original Message-
> > From: Peter Hutterer [mailto:peter.hutte...@who-t.net]
> > Sent: Tuesday, January 05, 20
you in advance.
JengHyun Kang.
> -Original Message-
> From: Peter Hutterer [mailto:peter.hutte...@who-t.net]
> Sent: Tuesday, January 05, 2016 5:46 PM
> Cc: wayland-devel@lists.freedesktop.org; sj76.p...@samsung.com;
> duna...@samsung.com
> Subject: Re: [libinput] How I get
nts, but Andreas Pokorny
has a number of patches to add extra axes for touch events. I think this one
was the last version:
http://lists.freedesktop.org/archives/wayland-devel/2015-November/025415.html
and the comments:
http://lists.freedesktop.org/archives/wayland-devel/201
Hello, guys.
I have a query regarding linux MT protocol event handling in libinput side.
I wanted to get the extra events such as ABS_MT_TOUCH_MAJOR,
ABS_MT_PRESSURE as an event of libinput,
but I found that libinput doesn't handle those events.
Thus I'd like to know whether there is any plan rega
re.
>>
>> Thanks & Regards,
>> Vikas
>>
>> On Mon, Dec 14, 2015 at 3:24 PM, Vikas Patil wrote:
>>> Hi Eugen Friedrich
>>>
>>> Thanks a lot for your quick reply.
>>>
>>> Attached here the file with WAYLAND_DEBUG=1 log wh
>
>> Attached here the file with WAYLAND_DEBUG=1 log when the gstreamer
>> plug-in is in use. I can see "ivi_input@18.input_focus(90, 4, 0)" for
>> the surface from plug-in but no touch events.
>>
>> Here is the output of APIs
>>
>> root@linux-9939-a1:
anagement-boun...@lists.genivi.org] On Behalf Of Vikas Patil
> Sent: Samstag, 12. Dezember 2015 12:57
> To: genivi-ivi-layer-managem...@lists.genivi.org; meta-
> freesc...@yoctoproject.org; Tanibata, Nobuhiko (ADITJ/SWG); Carlos Rafael
> Giani; wayland mailing list
> Subject: Touch events
Hi Eugen Friedrich
Thanks a lot for your quick reply.
Attached here the file with WAYLAND_DEBUG=1 log when the gstreamer
plug-in is in use. I can see "ivi_input@18.input_focus(90, 4, 0)" for
the surface from plug-in but no touch events.
Here is the output of APIs
root@lin
Dear All,
I am using wayland video sink (i.e. imxeglvivsink) from
gstreamer1.0-plugins-imx [1] to play the video along with weston 1.8.0
and wayland-ivi-extenstion 1.4.0. I have modified “imxeglvivsink” to
have the ilm and touch input support [2]. Basically I am posting touch
events on GST bus
Signed-off-by: Peter Hutterer
---
src/libinput.h | 28 +++-
1 file changed, 19 insertions(+), 9 deletions(-)
diff --git a/src/libinput.h b/src/libinput.h
index f978b37..356c1bf 100644
--- a/src/libinput.h
+++ b/src/libinput.h
@@ -839,8 +839,11 @@ libinput_event_touch_get_
Signed-off-by: Peter Hutterer
---
src/evdev.c| 13 +
src/libinput-private.h | 6 ++
src/libinput.c | 23 +--
3 files changed, 16 insertions(+), 26 deletions(-)
diff --git a/src/evdev.c b/src/evdev.c
index d1b0504..cab7e85 100644
--- a/src/
Instead of device-specific coordinates that the caller can't interpret without
knowing the range anyway, return mm as the default value.
Signed-off-by: Peter Hutterer
---
src/evdev.h | 7 +++
src/libinput.c | 20
src/libinput.h | 32 ---
From: Ander Conselvan de Oliveira
That would be the case of a touch screen mapped to an output that was
unplugged.
---
src/libinput-device.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/src/libinput-device.c b/src/libinput-device.c
index 0ca6c4b..a67c119 100644
--- a/src/libinput-devic
From: Ander Conselvan de Oliveira
That would be the case of a touch screen mapped to an output that was
unplugged.
---
src/libinput-device.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/src/libinput-device.c b/src/libinput-device.c
index 0ca6c4b..a67c119 100644
--- a/src/libinput-devic
On Sat, Feb 22, 2014 at 03:38:27PM +0100, Jonas Ådahl wrote:
> Since a Wayland compositor have to represent all touch devices of a seat
> as one virtual device, lets make that easier by also providing seat wide
> slots with touch events.
>
> Seat wide slots may be
Since a Wayland compositor have to represent all touch devices of a seat
as one virtual device, lets make that easier by also providing seat wide
slots with touch events.
Seat wide slots may be accessed using
libinput_event_touch_get_seat_slot().
Signed-off-by: Jonas Ådahl
---
Changes since v1
> as one virtual device, lets make that easier by also providing seat wide
> > > slots with touch events.
> > >
> > > Seat wide slots may be accessed using
> > > libinput_event_touch_get_seat_slot().
> > >
> > > Signed-off-by: Jonas Ådahl
> > slots with touch events.
> >
> > Seat wide slots may be accessed using
> > libinput_event_touch_get_seat_slot().
> >
> > Signed-off-by: Jonas Ådahl
> > ---
> > src/evdev.c| 24
> > src/evdev.h
On Wed, Feb 19, 2014 at 10:04:10PM +0100, Jonas Ådahl wrote:
> Since a Wayland compositor have to represent all touch devices of a seat
> as one virtual device, lets make that easier by also providing seat wide
> slots with touch events.
>
> Seat wide slots may be
Since a Wayland compositor have to represent all touch devices of a seat
as one virtual device, lets make that easier by also providing seat wide
slots with touch events.
Seat wide slots may be accessed using
libinput_event_touch_get_seat_slot().
Signed-off-by: Jonas Ådahl
---
src/evdev.c
On Wed, Feb 12, 2014 at 09:36:42PM +0100, Jonas Ådahl wrote:
> Since a Wayland compositor have to represent all touch devices of a seat
> as one virtual device, lets make that easier by also providing seat wide
> slots with touch events.
>
> Seat wide slots may be
Signed-off-by: Jonas Ådahl
---
src/evdev.c| 8 +---
src/libinput.h | 3 +++
2 files changed, 8 insertions(+), 3 deletions(-)
diff --git a/src/evdev.c b/src/evdev.c
index d8dff65..3fe28e4 100644
--- a/src/evdev.c
+++ b/src/evdev.c
@@ -163,7 +163,7 @@ evdev_flush_pending_event(struct evdev
Since a Wayland compositor have to represent all touch devices of a seat
as one virtual device, lets make that easier by also providing seat wide
slots with touch events.
Seat wide slots may be accessed using
libinput_event_touch_get_seat_slot().
Signed-off-by: Jonas Ådahl
---
src/evdev.c
. The WM needs to make the decision,
>> not the client.
>
> I'm pretty certain all touch events *MUST* go to the same surface until all
> touches are released. Otherwise it will be quite impossible to do gestures
> reliably, like the user could not do them to objects near the edge of
t the client.
I'm pretty certain all touch events *MUST* go to the same surface until
all touches are released. Otherwise it will be quite impossible to do
gestures reliably, like the user could not do them to objects near the
edge of a window.
No? I'm not sure what to say other than
Chase Douglas wrote:
The client won't see the third finger if it touches outside its window.
In the wayland case, only the WM has all the info needed to determine if
a touch is part of a global gesture. The WM needs to make the decision,
not the client.
I'm pretty certain all to
uch (down/up/motion/cancel
> >>>> events) interfaces
> >>>
> >>> [snip]
> >>>
> >>> So the client window will receive touch events without delay, but may
> >>> receive a cancel? I am in favor of this approach, but you
On 02/21/2012 09:15 PM, Bill Spitzak wrote:
> Daniel Stone wrote:
>> Hi,
>>
>> On 22 February 2012 00:13, Bill Spitzak wrote:
>>> It seems like it would be better if clients got the touch events first, and
>>> the compositor only did things if the client sai
On Wed, Feb 22, 2012 at 1:21 AM, Daniel Stone wrote:
> Because for a three-finger swipe, there
> will be a time when there's only one finger down, or two. At which
> point the client will say, 'ah yes, I'm interested in this!'. And
> then the third finger lands and you regret a terrible design
Daniel Stone wrote:
Hi,
On 22 February 2012 00:13, Bill Spitzak wrote:
It seems like it would be better if clients got the touch events first, and
the compositor only did things if the client said it was uninterested in the
events. For a lot of touch events this can be decided immediately
ncel
>>>>> events) interfaces
>>>>
>>>> [snip]
>>>>
>>>> So the client window will receive touch events without delay, but may
>>>> receive a cancel? I am in favor of this approach, but you need to add a
>>>> way to
Hi,
On 22 February 2012 00:13, Bill Spitzak wrote:
> It seems like it would be better if clients got the touch events first, and
> the compositor only did things if the client said it was uninterested in the
> events. For a lot of touch events this can be decided immediately on the
>
It seems like it would be better if clients got the touch events first,
and the compositor only did things if the client said it was
uninterested in the events. For a lot of touch events this can be
decided immediately on the touch-down, since the client knows the user
is pushing nothing.
I
on/button/axis events, set_pointer_surface request),
>>>> wl_keyboard (enter/leave/key events... what else... unicode event,
>>>> set_map request? pending kb work), and wl_touch (down/up/motion/cancel
>>>> events) interfaces
>>>
>>> [snip]
>>>
On terça-feira, 21 de fevereiro de 2012 21.49.26, Chase Douglas wrote:
> That doesn't make any sense. What if I'm playing a game? Latency
> matters, and I need to know that the touches are mine early on. In the
> case of a game, the environment should leave touches alone and
> immediately tell the
st),
>>> wl_keyboard (enter/leave/key events... what else... unicode event,
>>> set_map request? pending kb work), and wl_touch (down/up/motion/cancel
>>> events) interfaces
>>
>> [snip]
>>
>> So the client window will receive touch events without delay
ode event,
>> set_map request? pending kb work), and wl_touch (down/up/motion/cancel
>> events) interfaces
>
> [snip]
>
> So the client window will receive touch events without delay, but may
> receive a cancel? I am in favor of this approach, but you need to add a
>
b work), and wl_touch (down/up/motion/cancel
> events) interfaces
[snip]
So the client window will receive touch events without delay, but may
receive a cancel? I am in favor of this approach, but you need to add a
way to tell the window when the window manager has "rejected"
mentioned) but I am not quite sure
how that could be achieved. Suggestions are welcome.
Regards,
Laszlo
-Original Message-
From: ext Chase Douglas
Sent: 05/07/2011, 19:08
To: Agocs Laszlo.P (Nokia-MP-Qt/Tampere)
Cc: wayland-devel@lists.freedesktop.org
Subject: Re: [PATCH] Add touch events
With the exception of incoming phone call scenario, how does one go about
cancelling a touch event anyways? Unless I'm wildly mistaken, this is an
unlikely scenario. The way you normally cancel touch events is you touch
down on a button, then move your finger off the button and lift up, but
t; since we don't have the old X cruft to deal with.
>>>
>>> Yes, any stream of touch event, no matter how long, can be cancelled
>>> by the compositor at any time. The use cases are when the compositor
>>> recognizes a global gesture (three finger pinch to
1e2622e3cde6062e156b59a83b50e03 Mon Sep 17 00:00:00 2001
>>>> From: Laszlo Agocs
>>>> Date: Wed, 29 Jun 2011 17:51:29 +0300
>>>> Subject: [PATCH] Add touch events to protocol.
>>>>
>>>> ---
>>>> protocol/wayland.xml | 39
;>> From: Laszlo Agocs
>>> Date: Wed, 29 Jun 2011 17:51:29 +0300
>>> Subject: [PATCH] Add touch events to protocol.
>>>
>>> ---
>>> protocol/wayland.xml | 39 +++
>>> 1 files changed, 39 inserti
On Tue, Jul 5, 2011 at 1:08 PM, Chase Douglas
wrote:
> Hi Laszlo,
>
> On 06/29/2011 07:54 AM, Laszlo Agocs wrote:
>>
>> From f656362511e2622e3cde6062e156b59a83b50e03 Mon Sep 17 00:00:00 2001
>> From: Laszlo Agocs
>> Date: Wed, 29 Jun 2011 17:51:29 +0300
>&g
Hi Laszlo,
On 06/29/2011 07:54 AM, Laszlo Agocs wrote:
>
> From f656362511e2622e3cde6062e156b59a83b50e03 Mon Sep 17 00:00:00 2001
> From: Laszlo Agocs
> Date: Wed, 29 Jun 2011 17:51:29 +0300
> Subject: [PATCH] Add touch events to protocol.
>
> ---
> pro
From f656362511e2622e3cde6062e156b59a83b50e03 Mon Sep 17 00:00:00 2001
From: Laszlo Agocs
Date: Wed, 29 Jun 2011 17:51:29 +0300
Subject: [PATCH] Add touch events to protocol.
---
protocol/wayland.xml | 39 +++
1 files changed, 39 insertions(+), 0
49 matches
Mail list logo
