eGalax touchscreen calibration

[bboyandru]

(9th Jul, 2013 10:23 PM)Markamc Wrote:  

(9th Jul, 2013 10:02 PM)bboyandru Wrote:  

(9th Jul, 2013 09:31 PM)Markamc Wrote:  Hi Andrei,

Nice one, I'll try it later.

How do you do the calibration, is it using a program?
It would be possible to script and inject gestures too in python at the event level, although I don't intend on doing it! (need life back!)

The reason I tried a different way was the click_confines was to small for my finger size on a 7" screen, can you change this externally, say in the calib file so I could alter the sensitivity of a touch? Saves me recompiling.

Brantje, I'm sure the calibration should'nt be off, I think the clue was the resolution of your pi, xres 1240. The 'lag' I noticed was probably due to the python error

Hi Mark!

I did my calibration in Xserver using xinput_calibrator program(you can see how I did this on my blog post at the calibration part). I am sure that this can be done as well with ts_calibrate. If you want to disable my calibration you just have to put the values from the calibration file like this:
calib_x_d=<your screen resolution width> e.g. calib_x_d=1280
calib_y_d=<your screen resolution height> e.g. calib_y_d=720
calib_x_fact=-1
calib_y_fact=-1
My projection is like this:
pointer.x = screen_width - value_read.x * calib_x_fact - calib_x_d;
pointer.y = screen_height - value_read.y * calib_y_fact - calib_y_d;
and the original code is like this:
pointer.x = value_read.x;
pointer.y = value_read.y;
I will modify the patches and add click_confines value to the calibration file this evening.

Andrei

Yep, I did it like this too , would be good to use ts_calibrate then you could call it from a xbmc plug-in, the values are easy to translate.

Your patch is also on xbian at the moment, but with the single-click disabled, I was using the calib files until I tried a different way.

I meant, I force touch events and BTN_right events outside XBMC with uimapper, if your patch is permanent then I would have conflicting events for uimapper and your hard-coded patch. Would be nice, for me anyway, to choose which way? by some a 'flag' in the calib file, maybe?

I don't think my patch will affect forcing other inputs using uimapper. My code just skips the first point received by XBMC and use it as the previous point for distance calculation. For example, at one touch on the touchscreen, XBMC gets more than 5 events, so ignoring the first one wouldn't be a problem.
Please have a look at my description from the blog post:

Quote:After I have successfully calibrated the touchscreen I have discovered that single click was not possible from the touchscreen, just double click. After digging through the code, I have found that this was caused by drag action which was triggered because the previous values of the touch were far(more than 5 pixels) from a new press. For example, at the start of the program, cursor is set at 0,0 coordinates; if user is trying to press a button, let's say at 100, 300, the program(XBMC) will calculate the distance between these two points and will find out that this is greater than 5.
Pythagorean theory:
(100-0)x(100-0) + (300 - 0)x(300-0) is greater than 5x5 so XBMC will treat this as a drag event.

This drag issue is not caused when you double click, because the previous point in the second click action is very close to the second click point. This also works for mouses, because the previous value of the pointer is always very close to the new value of the pointer(because mouse's pointer drags on the screen and it doesn't jump - so each new value is very close to the previous one).

Andrei