I know that in Beta software, chasing gremlins is all part of the fun. That said, is this the proper place to report such findings?
On to the point of this post…
Thank you for providing a standardized calibration mechanism.
The following are my observations with CalibrateWindow.
The calibration points immediately register on TouchDown.
I have found that if the stylus bounces (perhaps I should lay off the caffeine) the next calibration point is registered.
This throws off the whole calibration, making it impossible to tap the “Exit” or “Start Again” buttons. The only option is a complete reset.
I propose that TouchUpEvent facilitate the trigger. This would allow the operator to precisely target the calibration point.
Additionally, perhaps an optional, “Keep calibration” dialog with 15 second timeout is warranted, and/or logic that determines when calibration points are too close for the given screen size.
Last, I propose the relabeling of the “Start Anyway” button to “Recalibrate” and “Exit” to “Done” in effort to better blend into an application’s UI.