Actually how about this. What if I create a little app called moblin-touchtimeout which pops up a dialog asking if the user wants to keep the touchscreen calibration settings or revert back to the old. Then, when the user touches the four points, the applet will add this program to the autostart folder for the desktop and reboot the GUI. Then when the GUI comes up with the new calibration settings in place, if the user messed up they won't be able to press the "Accept" button, it will timeout, revert, and restart the GUI again with the old settings.
It's a longer path than we would get in Hardy but it's the same basic behavior. What do you think?
Actually how about this. What if I create a little app called moblin-touchtimeout which pops up a dialog asking if the user wants to keep the touchscreen calibration settings or revert back to the old. Then, when the user touches the four points, the applet will add this program to the autostart folder for the desktop and reboot the GUI. Then when the GUI comes up with the new calibration settings in place, if the user messed up they won't be able to press the "Accept" button, it will timeout, revert, and restart the GUI again with the old settings.
It's a longer path than we would get in Hardy but it's the same basic behavior. What do you think?