On Fri, Jun 27, 2003 at 12:27:39PM +0200, Robert Woerle wrote: >> I guess everyone just wants to take the quick and dirty >>approach of communicating directly with the driver. >> >well ... i am no hardcore X- hacker , but i know how to survive and you >are right that this is a major issue >for touchscreen and probably some other Input drivers ... > >I did that hack , because from my point of view X is very very weak in >taking options on the fly ( or it is just not documented... or i just >didnt found it ) >Lagging these functionality , X misses a huge item of comfort for most >of the users ...
The point I'm making is that this isn't the first time that input device calibration has come up as an issue over the last few years. If everyone who runs into this problem chooses the quick and dirty approach, then it will never really be solved. It's a mistake to expect that "someone else" will have done it for you. Solving problems like this is a great way to make a valuable and lasting contribution to XFree86. People solving problems they ran into is what created XFree86 in the first place, and most of us were not "hardcore X-hackers" when we did that. >it would be nice to get a function which is able to just reread the >XF86Config at runtime and makes the values readable within the drivers ... >then anybody can use it or not in their drivers ... >the next thing i am really missing is a clear SIGNAL thing for input >drivers where i can query the driver from within a X-client ... XFree86 has some mechanisms for modifying configuration at run-time, but they are limited. One of the goals for XFree86 5.0 is to rework all of this to maximise run-time configuration flexibility. This also fits in with a related goal of making the XFree86 configuration file more of a preferences file. Achieving all of that is going to be a lot of work. In the meantime, it shouldn't be too difficult to propose/implement either a calibration enhancement to the XInput extension, or extend the new message passing facility in the XFree86-Misc extension to handle input drivers. I'm not sure which option would be best, and feedback from others with input driver experience would be helpful. David -- David Dawes Founder/committer/developer The XFree86 Project www.XFree86.org/~dawes _______________________________________________ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
