On Wed, Jun 04, 2014 at 08:00:17AM +1000, Peter Hutterer wrote:
On Tue, Jun 03, 2014 at 10:42:50PM +0200, Jonas Ådahl wrote:
On Tue, Jun 03, 2014 at 03:34:56PM +1000, Peter Hutterer wrote:
Now that we have run-time changes of the tap.enabled state move the check
to the IDLE state only.
On Wed, Jun 04, 2014 at 11:17:58AM +1000, Peter Hutterer wrote:
On Tue, Jun 03, 2014 at 10:41:16PM +0200, Jonas Ådahl wrote:
On Tue, Jun 03, 2014 at 03:34:55PM +1000, Peter Hutterer wrote:
Provide an interface to enable/disable tapping, with a default mapping of
1/2/3 fingers mapping to
Hi,
On 06/04/2014 10:21 AM, Jonas Ådahl wrote:
On Wed, Jun 04, 2014 at 11:17:58AM +1000, Peter Hutterer wrote:
On Tue, Jun 03, 2014 at 10:41:16PM +0200, Jonas Ådahl wrote:
On Tue, Jun 03, 2014 at 03:34:55PM +1000, Peter Hutterer wrote:
Provide an interface to enable/disable tapping, with a
Hi,
On 06/03/2014 07:34 AM, Peter Hutterer wrote:
Provide an interface to enable/disable tapping, with a default mapping of
1/2/3 fingers mapping to L/R/M button events, respectively.
Signed-off-by: Peter Hutterer peter.hutte...@who-t.net
---
src/libinput-private.h | 13 +
On 4/06/2014 18:40 , Hans de Goede wrote:
Hi,
On 06/03/2014 07:34 AM, Peter Hutterer wrote:
Provide an interface to enable/disable tapping, with a default mapping of
1/2/3 fingers mapping to L/R/M button events, respectively.
Signed-off-by: Peter Hutterer peter.hutte...@who-t.net
---
Hi,
On 06/03/2014 07:34 AM, Peter Hutterer wrote:
Now that we have run-time changes of the tap.enabled state move the check
to the IDLE state only. Otherwise the tap machine may hang if tapping is
disabled while a gesture is in progress.
Two basic tests are added to check for the tap
Hi,
On 06/03/2014 07:34 AM, Peter Hutterer wrote:
Provide an interface to enable/disable tapping, with a default mapping of
1/2/3 fingers mapping to L/R/M button events, respectively.
Signed-off-by: Peter Hutterer peter.hutte...@who-t.net
I see that in all the other config interfaces you
Hi,
On 06/03/2014 07:34 AM, Peter Hutterer wrote:
---
src/libinput-private.h | 9 ++
src/libinput.c | 35
src/libinput.h | 74
++
3 files changed, 118 insertions(+)
Looks good to me.
Regards,
Hi,
On 06/03/2014 07:34 AM, Peter Hutterer wrote:
Signed-off-by: Peter Hutterer peter.hutte...@who-t.net
---
src/evdev-mt-touchpad.c | 43 +++
src/evdev-mt-touchpad.h | 1 +
2 files changed, 44 insertions(+)
diff --git a/src/evdev-mt-touchpad.c
Hi,
On 06/03/2014 07:34 AM, Peter Hutterer wrote:
Signed-off-by: Peter Hutterer peter.hutte...@who-t.net
---
src/libinput-private.h | 9 +++
src/libinput.c | 33
src/libinput.h | 69
++
3 files
Hi,
On 06/03/2014 07:35 AM, Peter Hutterer wrote:
Only exposes two knobs - speed and precision which have historically been the
only two knobs exposed anyway on most UIs. We could go for something fancier
but really, I think this will be enough.
The only open question is whether speed will
On Wed, Jun 04, 2014 at 10:38:19AM +0200, Hans de Goede wrote:
Hi,
On 06/04/2014 10:21 AM, Jonas Ådahl wrote:
On Wed, Jun 04, 2014 at 11:17:58AM +1000, Peter Hutterer wrote:
On Tue, Jun 03, 2014 at 10:41:16PM +0200, Jonas Ådahl wrote:
On Tue, Jun 03, 2014 at 03:34:55PM +1000, Peter
Hi,
On 06/03/2014 07:35 AM, Peter Hutterer wrote:
Signed-off-by: Peter Hutterer peter.hutte...@who-t.net
---
src/libinput-private.h | 9 ++
src/libinput.c | 37
src/libinput.h | 77
++
3 files
Hi,
On 06/03/2014 07:35 AM, Peter Hutterer wrote:
---
src/libinput-private.h | 8
src/libinput.c | 33 ++
src/libinput.h | 54
++
3 files changed, 95 insertions(+)
diff --git
Hi,
On 06/04/2014 06:09 AM, Peter Hutterer wrote:
The direction lock was intended to avoid erroneous horizontal scroll events
when scrolling vertically (and vice versa). Some testing on my touchpad here
shows that it is too easy to accidentally lock the direction when no lock is
intended
Hi,
On 06/03/2014 07:35 AM, Peter Hutterer wrote:
---
src/libinput-private.h | 9
src/libinput.c | 33 +
src/libinput.h | 56
++
3 files changed, 98 insertions(+)
diff --git
When running gtk3-demo under weston opening comboboxes a second time
causes the program to bail due to weston returning an error. The
relevant client trace in this case is:
- xdg_shell@15.get_xdg_popup(new id xdg_popup@12, wl_surface@28,
- xdg_popup@12.destroy()
-
Signed-off-by: Hans de Goede hdego...@redhat.com
---
src/evdev-mt-touchpad-tap.c | 76 ++---
src/evdev-mt-touchpad.c | 1 -
src/evdev-mt-touchpad.h | 7 +
3 files changed, 10 insertions(+), 74 deletions(-)
diff --git
Hello,
I am running 2 operating systems in paralel on a Panda Board, Android and Linux
with Weston on it. Since Android doesn't have access to the GPU (it's one OS or
the other) I created proxy libs for EGL, GLESv1 and GLESv2 + gralloc(emulator
part).
So far all I was able to see on linux side
On Wed, Jun 04, 2014 at 12:54:58PM +1000, Peter Hutterer wrote:
On Tue, Jun 03, 2014 at 08:08:02PM -0400, Stephen Chandler Paul wrote:
Button states are applicable to more then just the pointer, so having a
non-generic name name for a generic enumerator value like
On Wed, Jun 04, 2014 at 11:10:35AM +0200, Hans de Goede wrote:
Hi,
On 06/03/2014 07:34 AM, Peter Hutterer wrote:
Now that we have run-time changes of the tap.enabled state move the check
to the IDLE state only. Otherwise the tap machine may hang if tapping is
disabled while a gesture is
On Wed, Jun 04, 2014 at 10:40:10PM +0200, Jonas Ådahl wrote:
On Wed, Jun 04, 2014 at 12:54:58PM +1000, Peter Hutterer wrote:
On Tue, Jun 03, 2014 at 08:08:02PM -0400, Stephen Chandler Paul wrote:
Button states are applicable to more then just the pointer, so having a
non-generic name name
On Wed, Jun 04, 2014 at 05:26:34PM +0200, Hans de Goede wrote:
Currently we are using DIY timers in the touchpad softbutton and tap handling
code, and at least the softbutton code gets its wrong. It uses one timer-fd
per touchpad to set a timeout per touch, which means that if a timeout is
set
On Thu, Jun 05, 2014 at 07:45:00AM +1000, Peter Hutterer wrote:
On Wed, Jun 04, 2014 at 10:40:10PM +0200, Jonas Ådahl wrote:
On Wed, Jun 04, 2014 at 12:54:58PM +1000, Peter Hutterer wrote:
On Tue, Jun 03, 2014 at 08:08:02PM -0400, Stephen Chandler Paul wrote:
Button states are applicable
On Thu, Jun 05, 2014 at 12:21:52AM +0200, Jonas Ådahl wrote:
On Thu, Jun 05, 2014 at 07:45:00AM +1000, Peter Hutterer wrote:
On Wed, Jun 04, 2014 at 10:40:10PM +0200, Jonas Ådahl wrote:
On Wed, Jun 04, 2014 at 12:54:58PM +1000, Peter Hutterer wrote:
On Tue, Jun 03, 2014 at 08:08:02PM
On Wed, Jun 04, 2014 at 10:57:36PM +0200, Jonas Ådahl wrote:
On Wed, Jun 04, 2014 at 11:10:35AM +0200, Hans de Goede wrote:
On 06/03/2014 07:34 AM, Peter Hutterer wrote:
[...]
@@ -583,9 +580,56 @@ tp_tap_handle_timeout(struct tp_dispatch *tp,
uint64_t time)
return tp-tap.timeout;
On Wed, Jun 04, 2014 at 05:26:34PM +0200, Hans de Goede wrote:
Currently we are using DIY timers in the touchpad softbutton and tap handling
code, and at least the softbutton code gets its wrong. It uses one timer-fd
per touchpad to set a timeout per touch, which means that if a timeout is
set
27 matches
Mail list logo
