Hello input people,
Recently I've been bringing up the touchstick hardware in the Dell
Latitude E7470 and have noticed that the existing drivers for this sort
of input device typically expose EV_REL events. Unfortunately,
it seems that exposing the hardware in this way leads to some rather
unfort
Peter Hutterer writes:
> On Sun, Jan 04, 2015 at 08:46:17PM -0500, Ben Gamari wrote:
>>
>> Hi Peter,
>>
>> Peter Hutterer writes:
[snip]
>> >
>> > yes, supposed to be handled by the rest of the stack. the X server doesn't
>> > change
Hi Peter,
Peter Hutterer writes:
> On Fri, Jan 02, 2015 at 01:49:01PM -0500, Ben Gamari wrote:
>
[snip]
>> If I place the monitor to the right of the panel, touches map to the
>> panel as expected. This isn't terribly surprising: the input presumably
>> has no i
Hello all,
My Latitude E7440 has a touch screen panel and a few external display
interfaces. I've noticed that when I plug in an external monitor touch
events no longer correspond to the location I have touched on the panel.
For instance, take the case where I have an external HDMI monitor with
Peter Hutterer writes:
>
> ok, what's happening here is that (most likely) the device is frozen.
> Event delivery works that for each event, dev->public.processInputProc
> is called. That is usually ProcessOtherEvents(), but if the device is
> frozen from a sync grab, that func is EnqueueEvents
Peter Hutterer writes:
> On 30/11/2013 02:42 , Ben Gamari wrote:
>> It seems that when keyboard input is in its paused state only the
>> device events are delivered. The core keyboard events are only
>> delivered after another mouse event has occurred.
>
> ok, what
Sorry, accidentally truncated log output.
Ben Gamari writes:
> Peter Hutterer writes:
>> you need to check again here. each event is processed twice, once for the
>> device and once for the master. you need to make sure that kbd->name ==
>> "Virtual core keyboar
Ben Gamari writes:
> Peter Hutterer writes:
>> you need to check again here. each event is processed twice, once for the
>> device and once for the master. you need to make sure that kbd->name ==
>> "Virtual core keyboard", you can ignore the actual devic
Peter Hutterer writes:
> On Fri, Nov 22, 2013 at 09:53:11AM -0500, Ben Gamari wrote:
[snip]
> you might want to build your server with debug symbols and install
> libunwind-devel, it'd help greatly with the backtrace.
>
Done.
[snip]
>> Note how `ActivateEarlyAccept
I recently took shipment of a Dell Latitude E7440 bearing a
touchscreen. While things work as expected under Unity, using
the touchscreen under XMonad causes the input system to quickly fall
apart. I've been trying to track this down in Bug #71878 [1]. I've been
putting my notes up in this bug whic
10 matches
Mail list logo
