Surface Sensors Reconnect when De/Attaching Touch Cover

Question

I'm developing a C++ app using various sensors.

When I de/attach my Touch Cover to my Surface Pro:
GetDefault() sometimes return nullptr as expected (actually not so expected though the sensors work again in a few seconds), but sometimes it throws access violation exception that even try-catch cannot catch; once a while my Surface Pro suddenly restarts when I de/attach my Touch Cover...

I call GetDefault() at every Direct3D update because de/attaching typing covers disconnect the sensors for a few seconds.

Is it possible to handle access violation exception? or should I exchange my Surface Pro instead?

Answer 1

I would start troubleshooting by not doing this: "I call GetDefault() at every Direct3D update "  That will be a ton of calls a second and you may be maxing out system resources.  Let's troubleshoot why you are getting the sensor behavior with a simplified demo of that problem (which you can post to SkyDrive) and others can use to troubleshoot this.

---

Jeff Sanders (MSFT)

@jsandersrocks - Windows Store Developer Solutions @WSDevSol
Getting Started With Windows Azure Mobile Services development? Click here
Getting Started With Windows Phone or Store app development? Click here
My Team Blog: Windows Store & Phone Developer Solutions
My Blog: Http Client Protocol Issues (and other fun stuff I support)