nanogui: Thread: Touch screen issues

Greg,

I am using a touch screen interface on an ARM processor using the tslib
interface.  We are using FLTK with Nxlib and linking the application to
the server. 

We need to be able to recalibrate the touch screen on the fly and have
the new calibration data accepted.

I have modified tslib to include the calibration routines found in
tscal, and provided a mechanism to turn on and off raw touch screen data
so we can correctly perform the calibration.  The problem is it appears
that we need to be able to reload the mouse driver for the new
calibration data to be used. 


I was considering adding a flag to GsSelect to indicate that the mouse
driver needed to be reloaded and then add a call there to reload the
mouse driver.  Is this the correct place for this.

Dave Leake 
Sensys Medical
dleake(at)sensysmedical.com

> I have modified tslib to include the calibration routines found in
tscal, and provided a mechanism to turn on and off raw touch screen data
so we can correctly perform the calibration.  The problem is it appears
that we need to be able to reload the mouse driver for the new
calibration data to be used. 

I'm not sure what you mean "reload the mouse driver."  The driver
is statically linked, so its already loaded.  Do you mean reload
the mouse calibration data?


> I was considering adding a flag to GsSelect to indicate that the mouse
driver needed to be reloaded and then add a call there to reload the
mouse driver.  Is this the correct place for this.

Probably not. Can you explain a bit more about how it is that
the system or user determines that a new calibration is needed,
and then effected?  There might be an event here we can hook
this into, or better yet an outside application that senses this and
sends a message to the server to reload its config data.

Regards,

Greg

> Can you explain a bit more about how it is that the system or user
determines that a new calibration is needed, and then effected? 

The user will determine when they want to recalibrate the screen.  
The Fltk Application will then execute the calibration sequence and
store the new calibration data.

> I'm not sure what you mean "reload the mouse driver."  The driver is
statically linked, so its already loaded.  Do you mean reload the mouse
calibration data?

At this time it appears we need to close and reopen the handle to the
linux touchscreen driver by calling GdMouseClose and then GdMouseOpen.
The new calibration values would then be used.
  
At the moment we can get upto storing the calibration data but, we have
to exit and restart the app for the calibration to become effective.

We are running with NONETWORK defined.

I have two simple functions that I have started with.
One allows the FLTK application to set a flag in nano-x to indicate the
mouse needs to be reconfigured.

The other function calls GrUnRegisterInput(mouse_fd), GdCloseMouse,
GdOpenMouse, and then GrRegisterInput(mouse_fd).  

Just trying to see where a good place to check for the flag would be.

Dave Leake