On Sat, 31 Mar 2001, Stefan Seefeld wrote:
> "Brian S. Julin" wrote:
> >
> > On Sat, 31 Mar 2001, Stefan Seefeld wrote:
> > > libGII contains an input module for linux evdev.
> > > What's the status of that ? How can I configure that ?
> >
> > It should be as simple as "export GII_INPUT=linux-evdev",
> > or if you are running a LibGGI application (more likely)
> > "export GGI_INPUT=linux-evdev". Assuming you have a working
> > LibGGI installation and a working display target, try running
> > the inputdump demo in lib/libggi.out/programs/util/ after
> > doing this and see if you get results. If it doesn't work,
> > it is possible the evdev IOCTLs have changed and the target
> > will need updating to work with your kernel.
>
> ok, I'm running linux 2.4.2, and it appears to work fine.
> Congrats !
>
> However, /dev/input/event0 appears to only provide half of the data.
> All I get is pressure and tilt values, as well as button events. I'm
> totally missing positional information. I guess that's what the other
> (logical) devices are for (/dev/input/mouse0, /dev/input/mice)
>
> > > May be the relevant documentation is even contained in some hidden corner
> > > in the docs. But a) the docs don't appear to be terribly well maintained,
> > > and b) the ggi-project home page has been unaccessible for a couple of
> > > weeks. Oh well...
> >
> > See lib/libgii/doc/inputs.txt
>
> that looks like a good start, but it is still unclear where I need to put these
> things.
> For my specific case (wacom stylus/eraser/cursor over usb), what do I need to do,
> to read events from all three device descriptors (/dev/input/[event0, mouse0, mice])
>?
I guess what you need is the wapcom mouse-protocol, which isn't
implemented yet AFAIK. Have a look at the source of gpm. It should
provide all information you need...
CU,
Christoph Egger
E-Mail: [EMAIL PROTECTED]
