Makes it even longer, but at least it's consistent with button and key state.
Signed-off-by: Peter Hutterer
---
sorry, another API change.
src/evdev-tablet.c | 4 ++--
src/libinput.c | 6 +++---
src/libinput.h | 8
test/tablet.c | 28 ++--
to
On Sun, Jan 03, 2016 at 10:07:42PM -0800, Bill Spitzak wrote:
> On 01/03/2016 08:21 PM, Peter Hutterer wrote:
> >On Fri, Jan 01, 2016 at 04:54:14PM +, Daniel Stone wrote:
> >>
> >>I almost wonder if we couldn't make peoples' lives easier by merging
> >>locking and confinement into a single inte
On Tue, Jan 05, 2016 at 12:05:17AM +, Caibin Chen wrote:
> The reason why it's annoying to me is that often time I tap something and
> move the cursor immediately. For example closing a browser tab then move
> back to the content. This triggers tap-and-drag unexpectedly.
the timeout is current
On Tue, Jan 05, 2016 at 09:21:27AM +0800, Jonas Ådahl wrote:
> On Mon, Jan 04, 2016 at 02:21:37PM +1000, Peter Hutterer wrote:
> > On Fri, Jan 01, 2016 at 04:54:14PM +, Daniel Stone wrote:
> > > Hi,
> > > A couple of (belated) comments ...
> > >
> > > On 3 December 2015 at 07:28, Jonas Ådahl
On Sun, Jan 03, 2016 at 10:37:47PM -0800, Bill Spitzak wrote:
> On 01/03/2016 10:28 PM, Peter Hutterer wrote:
>
> >>I really do not like this key assignment being something the compositor is
> >>in charge of. A client may have a very good reason to use middle-click for
> >>something else, yet stil
This patchset adds pressure thresholds handling for tools. Rather than
relying on BTN_TOUCH being set by the kernel, we look at the pressure and
generate our tip events based on that. Long-term this can be
device-specific, right now we just use 5%.
One major functional change: this means tip even
On tablets with ABS_PRESSURE use a pressure value to determine tip state, not
BTN_TOUCH. This enables us (down the road) to have device-specific pressure
thresholds. For now we use a 5% default for all devices.
The threshold is a range, if we go past the upper range we initiate the tip
down, if we
Signed-off-by: Peter Hutterer
---
src/evdev-tablet.c | 8
src/libinput-private.h | 2 +-
2 files changed, 9 insertions(+), 1 deletion(-)
diff --git a/src/evdev-tablet.c b/src/evdev-tablet.c
index 7804c91..7f6c860 100644
--- a/src/evdev-tablet.c
+++ b/src/evdev-tablet.c
@@ -882,6 +88
When we're only dealing with BTN_TOUCH we can make the tip event independent
of the axis event. Now that we handle pressure thresholds to trigger tip state
this does not work, we'd have to send an axis event with the new pressure and
then a tip event. Since the pressure triggers the tip event this
On Mon, Jan 04, 2016 at 02:21:37PM +1000, Peter Hutterer wrote:
> On Fri, Jan 01, 2016 at 04:54:14PM +, Daniel Stone wrote:
> > Hi,
> > A couple of (belated) comments ...
> >
> > On 3 December 2015 at 07:28, Jonas Ådahl wrote:
> > > +
> > > +
> > > + The lock_pointer request l
Preparation work for a pressure threshold where we can't just send a BTN_TOUCH
and expect it to trigger the tip event. So the event sequence now needs to
resemble the right order so the threshold will be triggered.
In some cases requires processing an axis event before the tip event. That
behavior
Signed-off-by: Peter Hutterer
---
src/evdev-tablet.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/src/evdev-tablet.c b/src/evdev-tablet.c
index 0c20483..426d83f 100644
--- a/src/evdev-tablet.c
+++ b/src/evdev-tablet.c
@@ -1049,6 +1049,9 @@ detect_pressure_offset(struct tablet_dispatch *
On Mon, Jan 04, 2016 at 02:09:16PM +1000, Peter Hutterer wrote:
> On Fri, Jan 01, 2016 at 04:00:33PM +, Daniel Stone wrote:
> > Hi Jonas,
> >
> > On 17 November 2015 at 10:09, Jonas Ådahl wrote:
> > > +
> > > +
> > > + [...]
> > > +
> > > + Relative motions are not coupl
On Mon, Jan 04, 2016 at 03:05:24PM +1000, Peter Hutterer wrote:
> On Fri, Dec 18, 2015 at 12:03:46PM -0500, Lyude wrote:
> > Signed-off-by: Lyude
> > ---
> > Changes
> > * Add new interfaces to replace reuse of wl_data_(source|offer)
> > * Get rid of the selection c
On Mon, Jan 04, 2016 at 02:21:37PM +1000, Peter Hutterer wrote:
> On Fri, Jan 01, 2016 at 04:54:14PM +, Daniel Stone wrote:
> > Hi,
> > A couple of (belated) comments ...
> >
> > On 3 December 2015 at 07:28, Jonas Ådahl wrote:
> > > +
> > > +
> > > + The lock_pointer request l
The reason why it's annoying to me is that often time I tap something and
move the cursor immediately. For example closing a browser tab then move
back to the content. This triggers tap-and-drag unexpectedly.
As of dragging without clicking the touchpad, I have a WIP branch adding
three-finger-to-
Hello. My computer has 2 seats. By seat I mean a set containing a
monitor, a videocard, a mouse, and a keyboard. I can drive them with 2
Xorg server, and I am looking for how to replicate this configuration
with Wayland.
AFAIK, Weston uses "libinput", so I assigned "WL_SEAT" of input devices
On 01/03/2016 08:21 PM, Peter Hutterer wrote:
On Fri, Jan 01, 2016 at 04:54:14PM +, Daniel Stone wrote:
I almost wonder if we couldn't make peoples' lives easier by merging
locking and confinement into a single interface, adding a bool for
whether or not to allow pointer movement (confine)
On 01/03/2016 10:28 PM, Peter Hutterer wrote:
I really do not like this key assignment being something the compositor is
in charge of. A client may have a very good reason to use middle-click for
something else, yet still want the ability to paste from the selection.
this is still possible wit
On 01/03/2016 09:05 PM, Peter Hutterer wrote:
On Fri, Dec 18, 2015 at 12:03:46PM -0500, Lyude wrote:
+This event is sent whenever the client receives a middle click, and
will
+be received by the client before the actual middle click event. While
+the compositor is free t
Without this 'proxy' argument, the '%p' formatter prints a constant
garbage value.
Signed-off-by: Victor Berger
---
src/wayland-client.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/src/wayland-client.c b/src/wayland-client.c
index 509be08..4f18d7e 100644
--- a/src/wayland
21 matches
Mail list logo
