On Mon, Feb 08, 2016 at 05:01:11PM -0800, Jason Gerecke wrote:
> On Tue, Feb 2, 2016 at 2:59 PM, Peter Hutterer
> wrote:
> > The Wacom tilt range is 64 degrees so we map everything into that until we
> > know otherwise.
> >
> > This commit also switches the tilt axes around to align the angles wi
The firmware version is in id.version, not id.model which is always
PSMOUSE_ALPS for ALPS devices.
The various fw versions are listed in /drivers/input/mouse/alps.h and
are all hex numbers. Version 8 is actually 0x800, change the match
accordingly.
Expected side-effect: earlier versions of ALPS t
https://bugs.freedesktop.org/show_bug.cgi?id=90590
Signed-off-by: Peter Hutterer
---
src/evdev-mt-touchpad.c| 3 ++-
src/evdev.c| 1 +
src/evdev.h| 1 +
udev/90-libinput-model-quirks.hwdb | 4
4 files changed, 8 insertions(+), 1 de
On Tue, Feb 2, 2016 at 2:59 PM, Peter Hutterer wrote:
> The Wacom tilt range is 64 degrees so we map everything into that until we
> know otherwise.
>
> This commit also switches the tilt axes around to align the angles with the
> x/y orientation, i.e. tilting the top of the stylus towards the pos
Hello,
while I developing the option 2. I raise few questions because this
option explicit the fact that back-ends does not share the same API (at
less for the configuration). To resolve the issue I found the following
options:
1. find a common configuration API (use key/value)
2. have th
On Fri, 2016-02-05 at 07:54 +0800, Jonas Ådahl wrote:
>
> On Feb 5, 2016 12:53 AM, "Rui Matos" wrote:
> >
> > The last cursor frame we commited before the pointer left one of our
> > surfaces might not have been shown. In that case we'll have a cursor
> > surface frame callback pending which we n
On Monday, 8 February 2016, Bill Spitzak wrote:
> On Mon, Feb 8, 2016 at 2:02 AM, Pekka Paalanen > wrote:
>
>> On Fri, 5 Feb 2016 21:03:20 +0100
>> Benoit Gschwind > > wrote:
>> > I will add my opinion as called for opinions. First I made a quick
>> > brainstorm following previous proposals abou
On Mon, Feb 8, 2016 at 7:07 PM, Bill Spitzak wrote:
> The x and y have to be signed. Imagine if the client is scrolled in such a
> way that the cursor rectangle is partially outside the surface.
Are you saying this is an acceptable case:
++
|compositor popup|
++
Hi All,
Just like last year there was a pre-fosdem cross desktop wayland meetup
on the Friday before fosdem.
Unfortunately this year we did not get as diverse a group
as last time. Here are some short notes in case anyone
is interested what was discussed.
Present were:
Derek Foreman (Samsung,
On 05/02/16 08:50 AM, Derek Foreman wrote:
> On 05/02/16 07:25 AM, Pekka Paalanen wrote:
>> From: Pekka Paalanen
>>
>> Since shm_pool_resize() uses mremap(MREMAP_MAYMOVE), the pool's base
>> address may change at that point.
>>
>> If a compositor stores the pointer and a client enlarges the pool,
Hi,
On 08-02-16 03:51, Peter Hutterer wrote:
If dwt is disabled on the commandline, e.g. by setting an xinput property it
may be disabled before the release event comes in. This caused the timer to
refresh indefinitely since the key state mask was still on for that key.
Always updating the key s
Hi,
Thanks for the update. I'm replying to both v4 and your reply to my
previous mail. Inline:
On Tue, Feb 2, 2016 at 2:33 PM, Jan Arne Petersen wrote:
> +
> +
> + Disable text input in a surface (typically when there is no focus on
> any
> + text entry inside the surface)
On Fri, 5 Feb 2016 21:03:20 +0100
Benoit Gschwind wrote:
> Hello,
>
> I will add my opinion as called for opinions. First I made a quick
> brainstorm following previous proposals about solutions available. I see
> 3 mains choice:
Hi,
thanks for looking into this.
> 1. a structure that user
On Sat, 6 Feb 2016 12:09:59 +0100
Quentin Glidic wrote:
> On 06/02/2016 06:07, Emmanuel Gil Peyrot wrote:
> > libjpeg is only used in shared/image-loader.c in weston, like libwebp
> > it doesn’t make sense to fail the entire build if it isn’t present, for
> > any reason.
> >
> > I kept libpng a h
On Fri, 5 Feb 2016 21:42:02 +
"Ucan, Emre (ADITG/SW1)" wrote:
> Hi Pekka,
>
> First Question:
> An ivi-layer should have properties so that a group of surfaces can
> be scaled and clipped according to destination and source rectangle
> of the layer.
>
> Second Question:
> We have requiremen
15 matches
Mail list logo