Re: settings for WaitCommEvent

Tech-Archive recommends: Fix windows errors by optimizing your registry

I have seen this happening on an HTC P3300 on the GPS port. There was nothing to be done but to revert to ReadFile with timeouts...
http://nativemobile.blogspot.com/2007_01_01_archive.html (Reading the GPS port on the HTC P3300)

João Paulo Figueira
DAD MVP
www.primeworks-mobile.com

"<ctacke/>" <ctacke[at]opennetcf[dot]com> wrote in message news:eZWarR0tHHA.4972@xxxxxxxxxxxxxxxxxxxxxxx
First:
My code calls SetCommMask, then WaitCommEvent. After WaitCommEvent has finished, do I need to re-call SetCommMask, or are the values still set? I found an example that called SetCommMask after WaitCommEvent completed, and I'm curious if that is something I should or should not be doing.

I always reset it to make sure the mask is correct.


Second:
Is there a way to specify a timeout for WaitCommEvent? Whenever my application exits, WaitCommEvent returns with FALSE (which causes my code to display an error) because there was not way to yank it out of its waiting state.

SetCommTimeouts

Third:
There are times that I *know* data is there! I can call other functions while WaitCommEvent is waiting for data, and they are able to pull in data while WaitCommEvent just sits there waiting for God knows what.

You're waiting on EV_DATA? Answer #1 might be applicable. I've never seen it not signal when data was available.


--

Chris Tacke, Embedded MVP
OpenNETCF Consulting
Managed Code in an Embedded World
www.OpenNETCF.com




.

Quantcast