I'm doing some IR communication at the TinyTP layer in order to talk to a third-party device. The trouble I'm having is that communication is very reliable on some Palms, and very unreliable on others. For example, we have an m505 that always communicates great, but we also have a Kyocera phone that hardly communicates at all.
I have a few questions: 1. Do I need to call EvtGetEvent regularly to make IR communications reliable? The reason I ask is that I have much better success with the Kyocera if I wait until the media is free between calling IrDiscoverReq and IrConnectIrLap, and the media doesn't free up unless I call EvtGetEvent. 2. Is there a function other than EvtGetEvent that I can use to give time to the IR media? Events are handled by a different part of my code, so I'd like to give time to the media without killing events in the process. 3. For debugging purposes, I print messages to a form. It seems that the Kyocera communication is slightly more reliable if I disable the print statements. Since some print statements can take 100 ms or more on the Kyocera, I'm wondering if some of the IR Comm functions are sensitive to timing, and if so, which ones? Craig -- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
