>>> Ville Syrjälä <[EMAIL PROTECTED]> 11/17/2008 9:39 AM >>> > I'm not sure if anyone has thought about using linux_input with > touchscreen devices. It does support touchpads but obviously the > touchscreens need proper calibration. Typically one would use > tslib for touchscreens. tslib already provides it's own calibration > support.
Agreed, but when I searched the tslib mailing list archives I found no mention of the model or company that makes the touchscreen I'm dealing with. The linux_input module found it and was able to use it right away. The only part that's missing is the calibration... if you can handle the support for touchscreens w/o tslib, why not add that one little bit? There are a bunch of comments in linux_input.c about trying to treat touchscreens like other devices, so someone obviously started down this path in the past. Besides, absolute value input w/o some sort of translation makes little to no sense anyway, so I'm sure this is an improvement of some sort. > AFAICS you should be able to use the EVIOCSABS ioctl to configure the > limits in the kernel driver instead of having to add new configuration > options to DirectFB. I would have thought so too, but it seems that the calibration utility that comes with my touchscreen doesn't use EVIOCSABS or EVIOCGABS. It makes me question whether this really would be "common" practice and how to expose these variables for everyone instead of just the controllers with calibration utilities which do use those two calls. > Getting the screen resolution from the mode= option is not a good idea. > >It sure does. The screen size should obviously come from the screen >code but that part of DirectFB is a bit thin and there's no support >for screen size change notifications at the moment. Adding them >shouldn't be difficult though. > >There's also the issue of multiple layers and layer positions. The >device coordinates should probably be scaled to screen coordinates first >and then translated/clipped to layer coordinates so that the windowstacks >will work properly. I haven't had time to dig into the libraries enough to find-out or even make the call to get me the current screen res. This is definitely above my head for now. I'll probably write the assumption or "hard code" some values for now - if someone can change these, please feel free as it will be a known issue/todo. I hope I can get to it, but since it's not critical path for my application, I doubt I'll be able to budget much time for it. Gareth Howlett Software Engineer, Sea Tel Products Cobham SATCOM Marine Systems (çy E-mail and any files transmitted with it (E-mail) is intended solely for the addressee(s) and may contain confidential and/or legally privileged information. If you are not the addressee(s), any disclosure, reproduction, copying, distribution or other use of this E-mail is prohibited. If you received this E-mail in error please delete it and notify the sender immediately via our switchboard at 01.925.798.7979 or via return E-mail. Neither the company, nor any individual sending this E-mail accepts any liability in respect of the content (including errors and omissions) and timeliness of this E-mail which arise as a result of this transmission. If verification is required, please request a hard copy version. This email was scanned by Postini, the leading provider in Managed Email Security. For more information visit www.groveis.com _______________________________________________ directfb-dev mailing list directfb-dev@directfb.org http://mail.directfb.org/cgi-bin/mailman/listinfo/directfb-dev
