On Thu, Mar 27, 2014 at 07:34:37PM +0600, Alexander E. Patrakov wrote:
> 2014-03-27 19:22 GMT+06:00 Alexander E. Patrakov :
>
> (regarding slow scrolling)
>
> > I don't think so. I have tried to reproduce the bug by hand. It still
> > exists, but ./tools/event-debug still picks the scrolling up
>
hey, sorry about the delay, I got moved to other stuff for a while and only
now just picked up libinput again.
On Sat, Feb 22, 2014 at 03:33:26PM +0600, Alexander E. Patrakov wrote:
> 2014-02-21 5:26 GMT+06:00 Peter Hutterer :
> > On Fri, Feb 21, 2014 at 01:29:05AM +0600, Alexander E. Patrakov wro
2014-02-21 5:26 GMT+06:00 Peter Hutterer :
> On Fri, Feb 21, 2014 at 01:29:05AM +0600, Alexander E. Patrakov wrote:
>> Vertical two-finger scrolling works, but is way too sensitive both
>> with constant deceleration 1.0 and with 0.3.
>
> that's a xf86-input-libinput bug, Benjamin fixed that but I f
2014-02-21 5:26 GMT+06:00 Peter Hutterer :
> Touchpad data is always subjective :) it depends on finger size,
> conductivity and a whole bunch of other factors. what does help though is
> having evemu recordings of certain events. They may still be subjective but
> they're reproducible, allowing us
On Fri, Feb 21, 2014 at 01:29:05AM +0600, Alexander E. Patrakov wrote:
> 20.02.2014 12:21, I wrote:
> >20.02.2014 11:14, Peter Hutterer wrote:
> >>On Wed, Feb 19, 2014 at 11:55:28AM +0600, Alexander E. Patrakov wrote:
> >>> From my experience with the Sony touchpad (Vaio Z23A4R laptop), I'd
> >>>sa
20.02.2014 12:21, I wrote:
20.02.2014 11:14, Peter Hutterer wrote:
On Wed, Feb 19, 2014 at 11:55:28AM +0600, Alexander E. Patrakov wrote:
From my experience with the Sony touchpad (Vaio Z23A4R laptop), I'd
say that it doesn't solve the whole problem. Here is what goes wrong
with the old synapt
On Thu, Feb 20, 2014 at 12:21:53PM +0600, Alexander E. Patrakov wrote:
> 20.02.2014 11:14, Peter Hutterer wrote:
> >On Wed, Feb 19, 2014 at 11:55:28AM +0600, Alexander E. Patrakov wrote:
> >>19.02.2014 04:52, Peter Hutterer wrote:
> >>>The set of touchpad patches I sent out recently already handle
20.02.2014 11:14, Peter Hutterer wrote:
On Wed, Feb 19, 2014 at 11:55:28AM +0600, Alexander E. Patrakov wrote:
19.02.2014 04:52, Peter Hutterer wrote:
The set of touchpad patches I sent out recently already handle this by
default. When the physical clickpad button is depressed, the driver picks
On Wed, Feb 19, 2014 at 11:55:28AM +0600, Alexander E. Patrakov wrote:
> 19.02.2014 04:52, Peter Hutterer wrote:
> >The set of touchpad patches I sent out recently already handle this by
> >default. When the physical clickpad button is depressed, the driver picks
> >the finger that is pressing the
19.02.2014 04:52, Peter Hutterer wrote:
The set of touchpad patches I sent out recently already handle this by
default. When the physical clickpad button is depressed, the driver picks
the finger that is pressing the button (sometimes guessing, but hey...).
That finger cannot control the pointer
On Tue, Feb 18, 2014 at 04:33:53PM +, Dominic Jänichen wrote:
> On Mon, 03 Feb 2014 11:02:42 +1000, Peter Hutterer wrote:
> >
> > tbh, I'm not planning to support every potential option under the sun.
> > There's a fine and rather blurry line between what is a preference and
> > what is merely
On Mon, 03 Feb 2014 11:02:42 +1000, Peter Hutterer wrote:
>
> tbh, I'm not planning to support every potential option under the sun.
> There's a fine and rather blurry line between what is a preference and
> what is merely configuration because we can't commit to a single
> default. I'd rather hav
On Sun, Feb 09, 2014 at 01:32:41PM +0100, Eugen Friedrich wrote:
>
>
> On 09.02.2014 05:10, Peter Hutterer wrote:
> >On Thu, Feb 06, 2014 at 11:28:49PM +0100, Eugen Friedrich wrote:
> >>Hi together,
> >>i would like to put some input from the embedded/ automotive perspective.
> >>
> >>you can thi
On 09.02.2014 05:10, Peter Hutterer wrote:
On Thu, Feb 06, 2014 at 11:28:49PM +0100, Eugen Friedrich wrote:
Hi together,
i would like to put some input from the embedded/ automotive perspective.
you can think about huge amount of different configurations for different
device types.
A lot of c
On Thu, Feb 06, 2014 at 11:28:49PM +0100, Eugen Friedrich wrote:
> Hi together,
> i would like to put some input from the embedded/ automotive perspective.
>
> you can think about huge amount of different configurations for different
> device types.
> A lot of configuration in the initial post dea
Hallo Jonas,
Thanks for fast replay, basically we have already proprietary
implementation in place to fulfil requirements from different customers.
Now we are looking forward to find a good open source component to
contribute our knowledge, experience and maybe code.
Since we using wayland, li
On Thu, Feb 06, 2014 at 11:28:49PM +0100, Eugen Friedrich wrote:
> Hi together,
> i would like to put some input from the embedded/ automotive perspective.
>
> you can think about huge amount of different configurations for different
> device types.
> A lot of configuration in the initial post dea
Hi together,
i would like to put some input from the embedded/ automotive perspective.
you can think about huge amount of different configurations for different
device types.
A lot of configuration in the initial post deals with behavior of buttons
and scrolling
areas of the touch panels.
The goo
2014-02-03 Peter Hutterer :
> On Fri, Jan 31, 2014 at 08:26:54PM +0600, Alexander E. Patrakov wrote:
>> Peter Hutterer wrote:
>> > I've been thinking about how to add a device configuration interface to
>> > libinput, and after getting feedback from Jonas and Benjamin, here's a
>> > proposal (no co
On Fri, Jan 31, 2014 at 08:26:54PM +0600, Alexander E. Patrakov wrote:
> Peter Hutterer wrote:
> > I've been thinking about how to add a device configuration interface to
> > libinput, and after getting feedback from Jonas and Benjamin, here's a
> > proposal (no code yet).
> >
> > First, I think t
Peter Hutterer wrote:
> I've been thinking about how to add a device configuration interface to
> libinput, and after getting feedback from Jonas and Benjamin, here's a
> proposal (no code yet).
>
> First, I think the configuration should be feature-specific, not device
> specific, so it is indepe
I've been thinking about how to add a device configuration interface to
libinput, and after getting feedback from Jonas and Benjamin, here's a
proposal (no code yet).
First, I think the configuration should be feature-specific, not device
specific, so it is independent of a classification or capab
22 matches
Mail list logo