Ok. I see how it works now. I missed the point where VR3 users started using the PicoGUI version of tpcal (in addition to the Agenda version if they use X and PicoGUI).
Does anybody still use the r3912ts driver? (I'm guessing not because there's a syntax error in "int r3912ts_fd_activate(int)" toward the end). Anyway, if someone does have a Helio and the tools to build a romdisk it might be worth trying out. The driver is nearly the same as the vr3ts, so it could be useful. Another thing to do is put some printf's or something to log the touchscreen activity (raw and filtered) to see where things are being blocked. As far as I can tell looking at the code, it should be getting something from the driver and sending it to the input filter. The worst that I can see is the possibility of flipping the x and y coordinates (see the VR-specific note about the way touch screen hardware measures voltage toward the end of the first vr3ts.c) which might very well be taken care of in a way that I missed. I'll pull out my VR3 on Tuesday or Thursday if no one else has any luck with it. -Sean ------------------------------------------------------- This sf.net email is sponsored by: OSDN - Tired of that same old cell phone? Get a new here for FREE! https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390 _______________________________________________ Pgui-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/pgui-devel
