From: Pekka Paalanen
Signed-off-by: Pekka Paalanen
---
COPYING | 22 --
Makefile.am | 29 ---
README | 17 +-
autogen.sh | 12 -
configure.ac | 72 --
src/Makefile.am | 37
src/compat-api.h | 106 -
src/wayland.c| 653 ---
Signed-off-by: Peter Hutterer
---
test/touchpad.c | 259
1 file changed, 259 insertions(+)
diff --git a/test/touchpad.c b/test/touchpad.c
index ea02f47..37df992 100644
--- a/test/touchpad.c
+++ b/test/touchpad.c
@@ -1623,6 +1623,255 @@
ST
Such jumps are usually consequences of the touchpad firmware failing to
notice that a different finger is in fact touching the touchpad.
This happens frequently when a finger is lifted at the same time as a
second finger is set down. Instead of a ABS_MT_TRACKING_ID of -1
followed by a new touchpoi
Prep work to avoid false positives in the upcoming touch-jump detection patch.
Signed-off-by: Peter Hutterer
---
test/touchpad.c | 32
1 file changed, 16 insertions(+), 16 deletions(-)
diff --git a/test/touchpad.c b/test/touchpad.c
index 7ff3d14..a6e2dd7 100644
Even if the button state differs, only send events if we claim we have a
button press or release queued up. Otherwise, skip over the event.
This cannot happen in the current code, it's prep-work for an upcoming patch.
Signed-off-by: Peter Hutterer
---
src/evdev-mt-touchpad-buttons.c | 36 +++
Rather than a random msleep() with a comment, use a helper function that
describes what we're waiting for. Also makes changing the timeouts easier in
the future.
Signed-off-by: Peter Hutterer
---
test/litest.c | 12
test/litest.h | 3 +++
test/touchpad.c | 42 ++
For some tests we need to string multiple event sequences together into one
event frame. Use a push/pop frame approach that stops litest from sending any
EV_SYN/SYN_REPORT events, so we can merge two touches together by e.g.
litest_push_event_frame(d);
litest_touch_down(d, 0, 10, 10);
litest_touch
Update the old_state once we've posted the respective buttons rather than
waiting for post_process to kick in. This allows calling our function multiple
times without double-posting the events.
Signed-off-by: Peter Hutterer
---
src/evdev-mt-touchpad-buttons.c | 7 +++
src/evdev-mt-touchpad.c
When a finger leaves the touchpad at the same time as another finger sets
down, a touchpad may not notice the change in fingers but rather think the
touchpoint moved to the new position. Bug 76722 has an event sequence but it
really boils down to just a move of a touch, identifiable only by the
di
From: Hans de Goede
The touchpad top softbuttons such as found on the Lenove T440 are intended for
use with the trackstick. Route their events through the trackstick, so that
they can be used for e.g. middle button scrolling with the trackstick.
Note that sending top button events to a disabled
On Tue, Sep 16, 2014 at 04:22:39PM +0200, Hans de Goede wrote:
> The touchpad top softbuttons such as found on the Lenove T440 are intended for
> use with the trackstick. Route their events through the trackstick, so that
> they can be used for e.g. middle button scrolling with the trackstick.
>
>
On Tue, Sep 16, 2014 at 04:22:36PM +0200, Hans de Goede wrote:
> Most trackpoint users want to be able to scroll using the trackpoint with
> the middle button pressed, add support for this.
>
> Signed-off-by: Hans de Goede
> Reviewed-by: Peter Hutterer
> ---
> include/linux/input.h| 1 +
>
On Wed, Sep 17, 2014 at 03:35:31PM +0200, Hans de Goede wrote:
> Make check_2fg_scroll functionality available outside of touchpad.c ,
> no functional changes.
>
> Signed-off-by: Hans de Goede
> ---
> test/litest.c | 39 +++
> test/litest.h | 1 +
> test/
On Wed, Sep 17, 2014 at 03:35:32PM +0200, Hans de Goede wrote:
> Signed-off-by: Hans de Goede
> ---
> test/Makefile.am | 5 +++
> test/litest-trackpoint.c | 2 +-
> test/litest.h| 1 +
> test/trackpoint.c| 100
> +++
>
On Wed, Sep 17, 2014 at 03:35:30PM +0200, Hans de Goede wrote:
> Make it easier to hit the topbutton area when the touchpad is disabled,
> normally we don't want to make the topbutton area too big, so as to not
> interfere with normal touchpad operation, but when disabled we have no such
> worries.
On Wed, Sep 17, 2014 at 11:16:06PM +0300, Giulio Camuffo wrote:
> 2014-09-17 23:11 GMT+03:00 Jonas Ådahl :
> > On Wed, Sep 17, 2014 at 10:56:13PM +0300, Giulio Camuffo wrote:
> >> I haven't looked at the implementation yet, just at the protocol, but
> >> isn't _wl_pointer_lock.lock_pointer() return
On Wed, Sep 17, 2014 at 09:55:36PM +0200, Axel Davy wrote:
> On 17/09/2014 21:39, Jonas Ådahl wrote :
> >Hi,
> >
> >This short series introduces a pointer lock interface based on the
> >previous proposal[0] by Kristian Høgsberg from last year. The first patch
> >adds a protocol more or less equal t
2014-09-17 23:11 GMT+03:00 Jonas Ådahl :
> On Wed, Sep 17, 2014 at 10:56:13PM +0300, Giulio Camuffo wrote:
>> I haven't looked at the implementation yet, just at the protocol, but
>> isn't _wl_pointer_lock.lock_pointer() returning a new wl_pointer a
>> problem? Objects should have a unique factory
On Wed, Sep 17, 2014 at 10:56:13PM +0300, Giulio Camuffo wrote:
> I haven't looked at the implementation yet, just at the protocol, but
> isn't _wl_pointer_lock.lock_pointer() returning a new wl_pointer a
> problem? Objects should have a unique factory interface, or else the
> version of the interf
I haven't looked at the implementation yet, just at the protocol, but
isn't _wl_pointer_lock.lock_pointer() returning a new wl_pointer a
problem? Objects should have a unique factory interface, or else the
version of the interface can't be determined.
--
Giulio
2014-09-17 22:39 GMT+03:00 Jonas
On 17/09/2014 21:39, Jonas Ådahl wrote :
Hi,
This short series introduces a pointer lock interface based on the
previous proposal[0] by Kristian Høgsberg from last year. The first patch
adds a protocol more or less equal to Kristians proposal, but moved out
of wl_seat into its own global object
Signed-off-by: Jonas Ådahl
---
clients/resizor.c | 62 +++
1 file changed, 62 insertions(+)
diff --git a/clients/resizor.c b/clients/resizor.c
index 19c6eeb..66e1c2f 100644
--- a/clients/resizor.c
+++ b/clients/resizor.c
@@ -219,13 +219,70 @@ s
Clients can lock the pointer surface wide, and receive relative pointer
events while the pointer is locked.
Signed-off-by: Jonas Ådahl
---
Makefile.am | 4 +-
clients/window.c | 177 +++
clients/window.h | 42 +
3 files chan
Introduce a pointer lock interface and implementation. The interface
consists of a global currently called _wl_pointer_lock. It is prefixed
with an underscore (_) in order to not conflict with a potential
official protocol in Wayland, and if moving it there, the prefixed
should be removed.
The pro
Hi,
This short series introduces a pointer lock interface based on the
previous proposal[0] by Kristian Høgsberg from last year. The first patch
adds a protocol more or less equal to Kristians proposal, but moved out
of wl_seat into its own global object (currently _wl_pointer_lock), with
some con
Good day, folks!
I'd like some light to be shed on the general area of GPU
hotplug/hotremoval, and in particular, on how this is supposed to affect
client persistence.
What is the state of multi-card output?
Is it possible to have drm_outputs replaced with (non-GL) clients surviving?
A specific
Make it easier to hit the topbutton area when the touchpad is disabled,
normally we don't want to make the topbutton area too big, so as to not
interfere with normal touchpad operation, but when disabled we have no such
worries.
Signed-off-by: Hans de Goede
---
src/evdev-mt-touchpad-buttons.c |
Make check_2fg_scroll functionality available outside of touchpad.c ,
no functional changes.
Signed-off-by: Hans de Goede
---
test/litest.c | 39 +++
test/litest.h | 1 +
test/touchpad.c | 49 -
3 files chan
Signed-off-by: Hans de Goede
---
test/Makefile.am | 5 +++
test/litest-trackpoint.c | 2 +-
test/litest.h| 1 +
test/trackpoint.c| 100 +++
4 files changed, 107 insertions(+), 1 deletion(-)
create mode 100644 test/trac
On Tue, 16 Sep 2014 19:13:15 +0200
Olivier Blin wrote:
> Hello,
>
> These small patches fix crashes in clients when some compositor
> interfaces are not available.
>
> This can occur when running the clients together with another
> compositor than weston, for example QWaylandCompositor without
On Tue, 16 Sep 2014 15:33:19 +0100
Steven Newbury wrote:
> On Tue, 2014-09-16 at 14:51 +0300, Pekka Paalanen wrote:
> > On Tue, 16 Sep 2014 13:26:12 +0200
> > Alexander Preisinger preisin...@gmail.com> wrote:
> >
> > > Hi pq,
> > >
> > > I use it in my wayland-next branch (for unstable wayland
31 matches
Mail list logo
