Re: How to run Weston on specific devices?

On Tue, 5 Jan 2016 00:08:56 +0200 m...@beroal.in.ua wrote: > 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. > >

[libinput] How I get extra touch events using libinput?

Hello, guys. I have a query regarding linux MT protocol event handling in libinput side. I wanted to get the extra events such as ABS_MT_TOUCH_MAJOR, ABS_MT_PRESSURE as an event of libinput, but I found that libinput doesn't handle those events. Thus I'd like to know whether there is any plan

Re: [PATCH wayland 1/2] protocol: Improve data source notification around DnD progress

On Wed, 23 Dec 2015 12:31:16 +0100 Carlos Garnacho wrote: > Hey, > > On Wed, Dec 23, 2015 at 5:47 AM, Jonas Ådahl wrote: > > Hi again, > > > > I was reading an E-mail in another thread that brought up different > > types of backward compatibility promises,

Re: [libinput] How I get extra touch events using libinput?

On Tue, Jan 05, 2016 at 05:01:33PM +0900, �� wrote: > Hello, guys. > I have a query regarding linux MT protocol event handling in libinput side. > I wanted to get the extra events such as ABS_MT_TOUCH_MAJOR, > ABS_MT_PRESSURE as an event of libinput, > but I found that libinput doesn't handle

[PATCH weston] compositor: create_data_source(): Fix potential crash on OOM

Noticed this while working on primary selection, in the event we run out of memory when trying to create a new data source, there's a chance we'll fail on wl_resource_create() and crash from source->resource being set to NULL. Signed-off-by: Lyude --- src/data-device.c | 10

Re: How to run Weston on specific devices?

Thank you for your answer. On 05.01.16 10:07, Pekka Paalanen wrote: On Tue, 5 Jan 2016 00:08:56 +0200 m...@beroal.in.ua wrote: 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

Re: [RFC v2] Add Primary Selection Protocol Version 1

Hello, On 5 January 2016 at 07:04, Bill Spitzak wrote: > On 01/04/2016 08:33 PM, Peter Hutterer wrote: > > Also it seems like you will send this on *every* middle click. Some > clients > require clicking the middle button a lot without pasting (it is very >

Re: [RFC v2] Add Primary Selection Protocol Version 1

On Mon, 2016-01-04 at 15:05 +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

Re: [PATCH libinput 3/5] tablet: add pressure threshold handling

'On Mon, Jan 4, 2016 at 5:21 PM, Peter Hutterer wrote: > 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.

Re: [PATCH libinput 4/5] tablet: a tip event can replace an axis event

On Mon, Jan 4, 2016 at 5:21 PM, Peter Hutterer wrote: > 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

Re: [PATCH libinput 0/5] tablet: pressure threshold handling

Largely looks good, aside from a few comments. For the series: Acked-by: Jason Gerecke Jason --- Now instead of four in the eights place / you’ve got three, ‘Cause you added one / (That is to say, eight) to the two, / But you can’t take seven from three,/ So

Re: [PATCH libinput] tablet: insert "STATE" into proximity/tip states

On Mon, Jan 4, 2016 at 8:48 PM, Peter Hutterer wrote: > Makes it even longer, but at least it's consistent with button and key state. > > Signed-off-by: Peter Hutterer > --- > sorry, another API change. Peter and the Amazing Technicolor

Re: libinput: Disable tap-and-drag

Peter Hutterer 于2016年1月4日周一 下午8:44写道： > the timeout is currently 300ms. Maybe we can reduce the timeout to provide > a > middle ground? > Worth a try, but we should seprate tap-and-drag timeout with drag-lock timeout. 300ms is sometime too short for me.

Re: [libinput] How I get extra touch events using libinput?

CC-ing Andreas this time, forgot about it in my original reply, sorry about that. On Wed, Jan 06, 2016 at 03:35:49PM +0900, 강정현 wrote: > Dear Peter and guys, > > thank you for your information about Andreas Pokorny's patches. > As I checked them out, most of them seem to make sense to me. :) >

[PATCH libinput] touchpad: fix DWT pairing for Macbook Pro 2015

From: Caibin Chen Label internal keyboards through the udev hwdb and only pair the internal (usb) Apple touchpads with those keyboards labelled as such. https://bugs.freedesktop.org/show_bug.cgi?id=93367 Co-authored-by: Peter Hutterer

RE: [libinput] How I get extra touch events using libinput?

Dear Peter and guys, thank you for your information about Andreas Pokorny's patches. As I checked them out, most of them seem to make sense to me. :) I have more queries. Would you please kindly answer to me? 1. How can we send the touch pressure/area events via wayland protocol? I know this

Re: libinput: Disable tap-and-drag

On Wed, Jan 06, 2016 at 05:28:30AM +, Caibin Chen wrote: > Peter Hutterer 于2016年1月4日周一 下午8:44写道： > > > the timeout is currently 300ms. Maybe we can reduce the timeout to provide > > a > > middle ground? > > > Worth a try, but we should seprate tap-and-drag timeout

Re: [RFC v2] Add Primary Selection Protocol Version 1

On 01/04/2016 08:33 PM, Peter Hutterer wrote: Also it seems like you will send this on *every* middle click. Some clients require clicking the middle button a lot without pasting (it is very common to use it as a pan control in 2D/3D). in the normal use-case you will get a lot more focus

Re: How to run Weston on specific devices?

On Tue, Jan 05, 2016 at 06:10:23PM +0200, m...@beroal.in.ua wrote: > Thank you for your answer. > > On 05.01.16 10:07, Pekka Paalanen wrote: > >On Tue, 5 Jan 2016 00:08:56 +0200 > >m...@beroal.in.ua wrote: > > > >>Hello. My computer has 2 seats. By seat I mean a set containing a > >>monitor, a

Re: [PATCH libinput] tablet: insert "STATE" into proximity/tip states

On Tue, Jan 05, 2016 at 11:59:20AM -0800, Jason Gerecke wrote: > On Mon, Jan 4, 2016 at 8:48 PM, Peter Hutterer > wrote: > > Makes it even longer, but at least it's consistent with button and key > > state. > > > > Signed-off-by: Peter Hutterer

Re: [PATCH libinput 4/5] tablet: a tip event can replace an axis event

On Tue, Jan 05, 2016 at 11:39:24AM -0800, Jason Gerecke wrote: > On Mon, Jan 4, 2016 at 5:21 PM, Peter Hutterer > wrote: > > 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

[PATCH v2 libinput 3/5] tablet: add pressure threshold handling

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