Evdev for a touchscreen w/ digitizer

[Peter Hutterer]

On Tue, Jun 05, 2012 at 11:28:20AM +0200, Cedric Sodhi wrote:
> On Tue, Jun 05, 2012 at 06:57:56PM +1000, Peter Hutterer wrote:
> > On Tue, Jun 05, 2012 at 10:14:02AM +0200, Cedric Sodhi wrote:
> > > > On Mon, Jun 04, 2012 at 09:36:10AM +0200, Cedric Sodhi wrote:
> > > > > On Mon, Jun 04, 2012 at 10:16:53AM +1000, Peter Hutterer wrote:
> > > > > > On Sun, Jun 03, 2012 at 09:54:28PM +0200, Cedric Sodhi wrote:
> > > > > > > Hello,
> > > > > > > 
> > > > > > > There is an EETI eGalax 0eef:a001 Touchscreen and a Wacpm 056a:0090
> > > > > > > ISDV4 stylus device.
> > > > > > > 
> > > > > > > Evtest output for a simple "tap" on the eGALAX is attached.
> > > > > > > 
> > > > > > > With Xorg 1.12.2, inputproto 2.2 on gentoo, "xinput list egalax" yields
> > > > > > > 
> > > > > > > eGalax_eMPIA Technology Inc. PCAP MultiTouch Controller id=13   [slave
> > > 
> > > Could you think of a reason why "xinput test" shows press & release
> > > events but "xev --root" does not? It appears that applications such as
> > > Openbox require events besides the XInput events to work, so when "xev
> > > --root" does not show any press & release events, certain things don't
> > > work.
> > 
> > xinput --test uses XI 1.x events and they work a bit differently than core
> > events. events are delivered from the window underneath the pointer upwards
> > to the root window until a client selected for those events on the window.
> > so if you run xev --root but anything below the root window selects for
> > button events you won't see them on the root window.
> > I suspect this is the case for you. start a plain xserver and then xev and
> > you'll likely see the events appear on the root window.
> 
> I don't know how "plain" it should have been, so I ran
> 
> "Xorg"
> 
> and then (from another VT)
> 
> "urxvt"
> 
> from wherein I executed xev -root. But tapping on the desktop, I still
> only get Motion Events.

yep, that's the right thing. alternatively, you can just run xinit, which
will start up xterm (or what's in your .xinitrc if you have one).

anyway, I'll try to run your event sequence tomorrow, maybe there's
some bug in the evdev driver. it looks ok on first glance.
 
Cheers,
  Peter