On Sat, Apr 18, 2015 at 04:53:46PM +0200, Carlos Garnacho wrote:
> Hey Jonas,
Hi,
Thanks for the explanations. I'll reply inline.
>
> On vie, 2015-04-17 at 15:50 +0800, Jonas Ådahl wrote:
>
>
> >
> > > For the touch case, depending on how the grab is implemented, with
> > > the
> > > curren
The single finger requirement dates back to when we couldn't configure the
scroll method. Now we can, so let's run the tests on as many suitable devices
as possible.
Signed-off-by: Peter Hutterer
---
test/touchpad.c | 10 +-
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/t
Just to make sure it is enabled (it should be anyway).
Signed-off-by: Peter Hutterer
---
test/touchpad.c | 17 +
1 file changed, 17 insertions(+)
diff --git a/test/touchpad.c b/test/touchpad.c
index 5ff4a36..aef8e1e 100644
--- a/test/touchpad.c
+++ b/test/touchpad.c
@@ -2638,12
The goal of this test is to make sure that the deltas are less than 5, which
is the scroll trigger for movement-based edge scrolling. The litest suite
takes percentages of the device, so use a scale factor to change how far we
move on the tablet. The wacom tablet is 141mm, the movement must be smal
https://bugs.freedesktop.org/show_bug.cgi?id=90070
Signed-off-by: Peter Hutterer
---
src/evdev-mt-touchpad-gestures.c | 6 ++
test/touchpad.c | 21 +
2 files changed, 27 insertions(+)
diff --git a/src/evdev-mt-touchpad-gestures.c b/src/evdev-mt-touchpad
Signed-off-by: Peter Hutterer
---
tools/shared.c | 29 +
tools/shared.h | 1 +
2 files changed, 30 insertions(+)
diff --git a/tools/shared.c b/tools/shared.c
index d8d23a7..e4d2804 100644
--- a/tools/shared.c
+++ b/tools/shared.c
@@ -46,6 +46,7 @@ enum options {
2015/04/21 5:42 "Bill Spitzak" :
>
> On 04/18/2015 03:20 AM, Hans de Goede wrote:
>
>> This has been discussed before, and as mentioned before I really
>> believe that we should not define a joystick API at all,
>> rather we should define an API which will allow an app to:
>>
>> 1) List devices whi
I've set up automatic builds of git snapshots of wayland, libinput, and
weston via Canonical's "recipe" PPA system:
https://launchpad.net/~wayland.admin/+archive/ubuntu/daily-builds
Builds are done once a day, if there are upstream changes since the last
build (so we've been getting about 1-2 b
A while back Pekka asked if I'd help look at xdg-shell and how we can
ensure it really does become a cross-desktop standard. I promised to
engage with the EFL folks and get their feedback, which I posted
recently.
I also promised to look at the Plasma team's comments on xdg-shell.xml
from some mo
Even the patches I did to the automatic documentation generation would
benefit greatly from this. There could be a clickable link from the
argument to the enumeration, or (with a good deal more work) it could
detect enums that are used only once and place them right there under
the arg.
And i
On 04/18/2015 03:20 AM, Hans de Goede wrote:
This has been discussed before, and as mentioned before I really
believe that we should not define a joystick API at all,
rather we should define an API which will allow an app to:
1) List devices which it can get raw access to
2) Request raw access,
On 04/20/2015 04:05 AM, Carlos Garnacho wrote:
- The last touch drags the window, the previous ones remain static and
are eventually lifted. Why do they apply where your finger no longer
is? Why do they apply at all? can one of these touches create an
xdg_popup (and another grab on another touch
Those touchpads presents an actual lower resolution that what is
advertised.
We see some jumps from the cursor due to the big steps in X and Y
when we are receiving data.
For instance, we receive:
E: 13.471932 0003 16366# EV_ABS / ABS_X16366
E: 13.471932 0003 0001 9591
Hi,
This is a new attempt to fix the X230 series.
This time, I tried to put some more scientific effort, and used gnuplot
to try to understand what was happening and how we could catch the same
acceleration at high speed than regular touchpads.
The results are synthetized in this png:
http://peo
X230 touchpads should be tagged as LIBINPUT_MODEL_LENOVO_X230 by udev to
apply a different acceleration profile.
Signed-off-by: Benjamin Tissoires
Reviewed-by: Peter Hutterer
---
changes in v4:
- renamed the file as 90-libinput-model-quirks.rules to give some space for
users to add their rules
On 04/18/2015 07:53 AM, Carlos Garnacho wrote:
Let me try to correct this by removing some unnecessary data. In
particular no list of actions is sent by the destination. Also there is
no need for the compositor to echo the selected action back to the
destination. More importantly I have added
The reason why the result is not output in the method is that it avoids
to have dependency on CAIRO. If user want to output it to file, user
shall link CAIRO on its controller.
ivi_layout_surface_get_size is also supported here because user needs
stride to call ivi_layout_surafce_dump.
Signed-off
On Mon, 20 Apr 2015 at 09:03 Pekka Paalanen wrote:
>
> Also, adding the strict type information to the XML spec has no benefit
> for C, which is the de facto language for Wayland core developers. A C
> compiler also does not raise errors if you violate the rules. This and
> all the above are the l
On 20 April 2015 at 14:49, x414e54 wrote:
>>> There is no sense in saying the sensor reading itself as absolute or
>>> relative. Either gives you some number in unknown units which you
>>> calibrate to get usable results. You have no idea where the stick is
>>> from the numbers you get. And there
On 20 April 2015 at 13:44, x414e54 wrote:
> This is kinda completely derailed from the whole include mice in the
> game controller protocol talk.
>
> On Mon, Apr 20, 2015 at 6:44 PM, Michal Suchanek wrote:
>> On 20 April 2015 at 10:48, Pekka Paalanen wrote:
>>> On Mon, 20 Apr 2015 10:13:34 +0200
>> There is no sense in saying the sensor reading itself as absolute or
>> relative. Either gives you some number in unknown units which you
>> calibrate to get usable results. You have no idea where the stick is
>> from the numbers you get. And there is absolutely no point caring. It
>> may have s
This is kinda completely derailed from the whole include mice in the
game controller protocol talk.
On Mon, Apr 20, 2015 at 6:44 PM, Michal Suchanek wrote:
> On 20 April 2015 at 10:48, Pekka Paalanen wrote:
>> On Mon, 20 Apr 2015 10:13:34 +0200
>> Michal Suchanek wrote:
>>
>>> On 20 April 2015
On vie, 2015-04-17 at 14:40 -0700, Bill Spitzak wrote:
> On 04/17/2015 05:16 AM, Carlos Garnacho wrote:
>
> > Let's expand on that example, maybe far-streched, but certainly
> > possible:
> > - I'm manipulating a client window with 2 fingers on the
> > touchscreen
> > (say zooming an image)
> >
On 20 April 2015 at 10:48, Pekka Paalanen wrote:
> On Mon, 20 Apr 2015 10:13:34 +0200
> Michal Suchanek wrote:
>
>> On 20 April 2015 at 09:36, Pekka Paalanen wrote:
>> > On Sun, 19 Apr 2015 09:46:39 +0200
>> > Michal Suchanek wrote:
>> >
>> >> So the device is always absolute and interpretation
On Mon, 20 Apr 2015 10:13:34 +0200
Michal Suchanek wrote:
> On 20 April 2015 at 09:36, Pekka Paalanen wrote:
> > On Sun, 19 Apr 2015 09:46:39 +0200
> > Michal Suchanek wrote:
> >
> >> So the device is always absolute and interpretation varies.
> >
> > I disagree.
> >
> > Let's take a mouse, opt
On Mon, Apr 20, 2015 at 4:36 PM, Pekka Paalanen wrote:
>> >> On 18 April 2015 at 16:58, x414e54 wrote:
>>
>> >>> USB HID specifications define a pointer and a mouse as two completely
>> >>> different inputs. A mouse can be a used as a pointer because it is
>> >>> pushing the cursor around but the
On Mon, 20 Apr 2015 09:43:42 +0200
Auke Booij wrote:
> On 20 April 2015 at 09:03, Pekka Paalanen wrote:
> > Hi,
>
> Thanks for taking the time to respond. I'll address your issues one by
> one, but the overarching picture is that such typing information
> should and would not be interpreted by
On 20 April 2015 at 09:36, Pekka Paalanen wrote:
>> >> On 18 April 2015 at 16:58, x414e54 wrote:
>>
>> >>> USB HID specifications define a pointer and a mouse as two completely
>> >>> different inputs. A mouse can be a used as a pointer because it is
>> >>> pushing the cursor around but the point
On 20 April 2015 at 09:03, Pekka Paalanen wrote:
> Hi,
Thanks for taking the time to respond. I'll address your issues one by
one, but the overarching picture is that such typing information
should and would not be interpreted by bindings as a promise, but
rather as a hint.
> I'm starting to thi
> >> On 18 April 2015 at 16:58, x414e54 wrote:
>
> >>> USB HID specifications define a pointer and a mouse as two completely
> >>> different inputs. A mouse can be a used as a pointer because it is
> >>> pushing the cursor around but the pointer points at a specific
> >>> location.
Okay. Using d
Hi,
On 20-04-15 00:40, Peter Hutterer wrote:
This is sort-of legitimate, so simply disable the axes and continue.
Any real axis we require to have a real range.
https://bugs.freedesktop.org/show_bug.cgi?id=90090
Signed-off-by: Peter Hutterer
Looks good:
Reviewed-by: Hans de Goede
Regards
On Sun, 19 Apr 2015 12:51:50 +
Jeroen Bollen wrote:
> Hello,
>
> It seems like this discussion died off. Currently there is no way to tell,
> from the Wayland XML specification whether an argument is a bitfield, or
> whether the argument takes an enum and what enum this is.
Hi,
I'm startin
32 matches
Mail list logo
