Unfortunately, we need the GPS to be on all the time as the users will be driving down the road collecting various attributes. Leaving the GPS off for the majority of the time just isn't feasible.
What is interesting, is we're using laptops with GOBI 2000 and 3000 chipsets which apparently have a really hard time keeping a decent GPS fix, even out in the open. We've hooked a generic USB GPS puck with a SiRF Star III chipset to one of the laptops and don't have nearly the issues we have with the GOBIs, but we still see it. It isn't even an issue with not having a GPS fix per se, but how the hardware handles losing that fix. The GOBIs almost seem to close the COM port for a second which fires the error in Mobile, whereas the SiRF chipset just sends NMEA sentences with no information. Unfortunately, we're locked in to having to use the built in GOBI hardware, so we need a way to intercept these error dialogs quietly in the background and keep trying the GPS.
This isn't an issue with the SDK, as I have no problem catching GPS errors in a friendly way...I just need to know how to do the same in the Mobile for Windows framework which is an entirely different animal when it comes to developing.
Thanks,
Doug