multi-touch-dev team mailing list archive

[Nuno Santos <nsantos@xxxxxxxxxx>]

Ok thanks,

I have the device working as a working pointer device as well now. Nice! :)

One more questions arises at this point. What is the best way of 
communicating with the device now?

I have a control panel that needs to change settings and instruct the 
driver to perform actions on the device.

My first try while developing this driver started with a simple usb 
driver example. That example had implemented the file open and close, 
write and read of the device thru the file system.

Should I use that same mechanism? Or is there any other way of doing it, 
more appropriated for an input device?

Thanks in advance,

With my best regards,

Nuno

On 11/10/2011 03:55 PM, Stephen M. Webb wrote:
> On 11/10/2011 10:29 AM, Nuno Santos wrote:
> > But...
> >
> > Can I interact with the operating system like I do with a mouse? What
> > event should I concern with?
> >
> > Should I look to any example in particular in linux input source for
> > touchscreens or any will do in general?
> Yes and no:  the X server interprets single-touch input as pointer
> events.  It is not exactly like a mouse, since a mouse is a relative
> device and usually has buttons, a touch is an absolute device that does
> not have buttons.
>
> Since the interpretation of war input events is done in the X server,
> you can look at the linux input source for any touchscreen for examples.
>   Your best bet is to follow the type B protocol documented in the kernel
> sources.