Hi,
On 04/24/2014 07:21 AM, Peter Hutterer wrote:
> On Tue, Apr 15, 2014 at 02:28:07PM +0200, Hans de Goede wrote:
>> We don't want touches in the button area to cause the pointer to move, add
>> a tp_button_touch_active function which the main code in evdev-mt-touchpad
>> can call to see if a tou
On Fri, Apr 25, 2014 at 08:27:17AM +0200, Hans de Goede wrote:
> Hi,
>
> On 04/24/2014 09:16 PM, Jonas Ådahl wrote:
> > On Tue, Apr 15, 2014 at 02:28:07PM +0200, Hans de Goede wrote:
> >> We don't want touches in the button area to cause the pointer to move, add
> >> a tp_button_touch_active funct
Hi,
On 04/24/2014 09:16 PM, Jonas Ådahl wrote:
> On Tue, Apr 15, 2014 at 02:28:07PM +0200, Hans de Goede wrote:
>> We don't want touches in the button area to cause the pointer to move, add
>> a tp_button_touch_active function which the main code in evdev-mt-touchpad
>> can call to see if a touch
On Tue, Apr 15, 2014 at 02:28:07PM +0200, Hans de Goede wrote:
> We don't want touches in the button area to cause the pointer to move, add
> a tp_button_touch_active function which the main code in evdev-mt-touchpad
> can call to see if a touch should be consider a candidate for being the
> pointe
On Tue, Apr 15, 2014 at 02:28:07PM +0200, Hans de Goede wrote:
> We don't want touches in the button area to cause the pointer to move, add
> a tp_button_touch_active function which the main code in evdev-mt-touchpad
> can call to see if a touch should be consider a candidate for being the
> pointe
We don't want touches in the button area to cause the pointer to move, add
a tp_button_touch_active function which the main code in evdev-mt-touchpad
can call to see if a touch should be consider a candidate for being the
pointer, should be taken into account for 2 finger scrolling, etc.
The idea
