Hi, please use reply-to-all.
On Tue, 1 Jul 2014 00:21:51 +0200
Fabrice Rey wrote:
> Thank you both for your constructive explanations.
>
> > "You are thinking in X11 terms now"
> I'm afraid; still, we'll probably have to think of some similar hints as
> "skip_taskbar/skip_pager", because there
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
---
Changes to v1:
- change to a simple enabled/disabled config
src/libinput-private.h | 13 +
src/libinput.c | 35
Signed-off-by: Peter Hutterer
---
Changes to v1:
- actually implement libinput_config_status_to_str
- add a basic test for it
src/libinput.c | 20
src/libinput.h | 33 +
test/misc.c| 23 +++
3 files changed, 76 insertio
Now that Hans is almost done with the touchpad accel code, let's get the
configuration interface in as well so we can tweak things at runtime.
This is the first configuration option that we actually need, I'll hold the
others back until the backend for them is more than a FIXME or hardcoded
values
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 default setting - which is now
"tap disabled by default", for t
> > The situation is getting even worse if you look at the feature which
> > Windows' Wacom driver has (I'm not sure whether this feature is available
> > in X11 Wacom driver, but it is highly requested by the painters). On
> > Windows the buttons on the stylus can be switched into "modifier" mode.
Motion starting inside the buttons is initially ignored. For pointer motion
along the negative y axis, the finger usually starts south of the touchpad
center. The more distance the motion is intended to cover, the closer to the
bottom edge of the touchpad the finger starts. For motions spanning mos
On Mon, Jun 30, 2014 at 11:41:08AM +0400, Dmitry Kazakov wrote:
> Hi, all!
>
> I will try to answer all your emails in one post.
>
> 1) Tablet vs. Touch. Basically what I am talking about is *not* touch
> arbitration and palm recognition. The Wacom driver itself blocks all the
> touch events when
On Mon, Jun 30, 2014 at 06:55:25PM -0700, Bill Spitzak wrote:
> On 06/30/2014 12:46 AM, Pekka Paalanen wrote:
>
> >>I was assuming the enter event contains enough information to know which
> >>device is causing it.
> >
> >It is the wl_pointer of a specific wl_seat:
> >http://people.collabora.com/~
On Mon, Jun 30, 2014 at 02:27:19PM +0200, Hans de Goede wrote:
> The old touchpad accel code was clamping touchpad acceleration between
> 0.2 and 0.4, and on the test devices I have the constant_factor ended up
> such that in practice the accel was almost always 0.2, so rather then having
typo: th
I have to disagree with a lot of this. The lack of window position is a
HUGE problem. We need to be able to save and restore user's preferences
for window arrangement. There is also a desire to port these window
arrangements between Windows and Linux.
The biggest problem is that you seem to th
On 06/30/2014 12:46 AM, Pekka Paalanen wrote:
I was assuming the enter event contains enough information to know which
device is causing it.
It is the wl_pointer of a specific wl_seat:
http://people.collabora.com/~jonny/protocol/wl_pointer.html#Event:enter
No information about the actual phys
On Mon, Jun 30, 2014 at 02:27:18PM +0200, Hans de Goede wrote:
> Once we get beyond the:
>
> if (abs(diff) <= margin)
> return center;
>
> test, then diff is either > margin or < -margin, otherwise the test would
> have triggered.
>
> So the "return center + diff;" at the end
Thank you both for your constructive explanations.
> "You are thinking in X11 terms now"
I'm afraid; still, we'll probably have to think of some similar hints as
"skip_taskbar/skip_pager", because there will be some windows we don't want
to see in the list of windows.
> "Btw. what if you start tw
I don't like it but, sure, it shouldn't break anything much further.
--Jason
On Mon, Jun 30, 2014 at 2:10 AM, Pekka Paalanen wrote:
> From: Pekka Paalanen
>
> If a client does this:
> 1. create a main window and map it
> 2. create a wl_surface, and make it a sub-surface of the main window
> 3.
It would be a good idea to add a pointer to this info somewhere on the
wayland web pages.
On 06/30/2014 01:01 AM, Ander Conselvan de Oliveira wrote:
On 06/29/2014 05:45 PM, Ayan Shafqat wrote:
Thanks for your prompt reply, Armin. I am familiar with git scm and have
used it for a few projects.
On Mon, 30 Jun 2014 20:46:46 +1000
Peter Hutterer wrote:
> On 30/06/2014 20:23 , Pekka Paalanen wrote:
> > On Mon, 30 Jun 2014 09:33:15 +0300
> > Pekka Paalanen wrote:
> >
> > If you have a tabletscreen, and your tool is a set of fingers, is it
> > any different to a touchscreen? Could we even c
Once we get beyond the:
if (abs(diff) <= margin)
return center;
test, then diff is either > margin or < -margin, otherwise the test would
have triggered.
So the "return center + diff;" at the end will never be reached, and the
"else if (diff < -margin)" can be turned into
The old touchpad accel code was clamping touchpad acceleration between
0.2 and 0.4, and on the test devices I have the constant_factor ended up
such that in practice the accel was almost always 0.2, so rather then having
a velocity based acceleration curve, in essence it was just always using an
ac
On 30/06/2014 20:23 , Pekka Paalanen wrote:
On Mon, 30 Jun 2014 09:33:15 +0300
Pekka Paalanen wrote:
On Mon, 30 Jun 2014 11:08:35 +1000
Peter Hutterer wrote:
On Sat, Jun 28, 2014 at 12:41:33PM +0300, Pekka Paalanen wrote:
On Fri, 27 Jun 2014 13:04:59 -0700
Bill Spitzak wrote:
On 06/26/2
On 30/06/2014 16:33 , Pekka Paalanen wrote:
On Mon, 30 Jun 2014 11:08:35 +1000
Peter Hutterer wrote:
On Sat, Jun 28, 2014 at 12:41:33PM +0300, Pekka Paalanen wrote:
On Fri, 27 Jun 2014 13:04:59 -0700
Bill Spitzak wrote:
[...]
- The pen moves the seat's mouse cursor, always. If more than
On Mon, 30 Jun 2014 09:33:15 +0300
Pekka Paalanen wrote:
> On Mon, 30 Jun 2014 11:08:35 +1000
> Peter Hutterer wrote:
>
> > On Sat, Jun 28, 2014 at 12:41:33PM +0300, Pekka Paalanen wrote:
> > > On Fri, 27 Jun 2014 13:04:59 -0700
> > > Bill Spitzak wrote:
> > >
> > > > On 06/26/2014 09:38 PM,
From: Pekka Paalanen
If a client does this:
1. create a main window and map it
2. create a wl_surface, and make it a sub-surface of the main window
3. set the sub-surface to desync
4. commit content to the sub-surface to map it
Then step 4 should cause the sub-surface to become mapped. However,
Hi, all!
I'd like to add about mapping of the tablet input.
In XInput one can assign a matrix transfromation for each tablet device,
which is exactly what people need. The usual usecase is the following:
A painter has a display + intuos tablet + cintiq. The external tablet is
mapped to the exter
On 06/29/2014 05:45 PM, Ayan Shafqat wrote:
Thanks for your prompt reply, Armin. I am familiar with git scm and have
used it for a few projects. What I am interested in are the points below:
(1) Coding style guidelines for Wayland.
(2) Where to submit patches.
The following document covers the
On Sun, 29 Jun 2014 23:43:21 -0700
Bill Spitzak wrote:
> On 06/29/2014 11:33 PM, Pekka Paalanen wrote:
>
> >> moving the visible cursor doesn't necessarily mean that it must translate
> >> into the wl_pointer protocol. It's probably awkward at first if the pointer
> >> moves and clients don't re
Hi, all!
I will try to answer all your emails in one post.
1) Tablet vs. Touch. Basically what I am talking about is *not* touch
arbitration and palm recognition. The Wacom driver itself blocks all the
touch events when the stylus is in the proximity, so it performs the
necessary arbitration. Wha
27 matches
Mail list logo
