I am working on a WinCE 6.0 system with a touch screen that stores calibration data (xy location, offset, etc.) in the system registry (HKLM \ HARDWARE \ TOUCH). Right now, I am putting cal values ββin registry keys that fall into the OS image during build. This works great for the monitor from which I get the original cal values, but when I download this image to another system with a different monitor, the location of the touch screen pointer is (understandably) turned off because the two monitors do not have the same cal values.
My problem is that I do not know how to store values ββin the registry correctly so that they are saved after the force cycle. Look, I can recalibrate the screen in the second system, but new values ββexist only in volatile memory. I suggested to my boss that we can simply tell our client to always leave power on the device - this did not work out well.
I need advice on how to save new constants in the registry so that we can calibrate the monitors once before sending them to our client, and I do not need to create separate OS images for each module we create.
The C # method, which is known to work in CE6.0, will be useful. Thank.
-Odbasta p>
source
share