RE: Setting touch calibration values after bootup
- From: Bill T <Bill T@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Tue, 3 Nov 2009 15:39:01 -0800
We had a similar situation that I was able to work around by creating a
driver that saves calibration settings on command and automatically restores
registry settings at boot when the driver loads. By setting the driver load
order so that it loads before our USB touchscreen driver, the settings are
available when needed. And a driver IOCTL is called to save settings after
running the vendor supplied calibration. Setting are saved in a CF file with
defaults specified in platform.reg in the event the file does not exist.
Although this isn't my preferred approach, it was easy to implement and
works well.
"Patrick Flanagan" wrote:
Hi,.
I'm trying to restore calibration data after a reboot due to a
non-persistent registry. Right now I write out the calibration data to a
file after the calibration routine is run, and then write the cal data in the
file out to the registry during future boot-ups. The issue is that the
driver loads the calibration data from the registry before my application has
a chance to restore the cal data from the persistent file. I've tried using
the TouchPanelSetCalibration() function with my data, but the calibration
settings don't change after the function is called. I've found posts in
other forums that recommend running an app that loads the persistent values
to the registry before the gwes loads, but I'd prefer to avoid that solution.
Thanks for any assistance.
- Prev by Date: Re: PlatformBuilder with subprojects Need Help
- Next by Date: bsquare's atom ce6 bsp can support sata?
- Previous by thread: Micro SD HC 16 Gb
- Next by thread: bsquare's atom ce6 bsp can support sata?
- Index(es):
Relevant Pages
|