>Now to answer your question. You can open the IR Library to prevent
incoming
>beams. There may be a better way, but I know that works
Didn't think of that.
>You could read the prefBeamReceive preference, set it to false, and then
reset it to what it
>was when you're done. That should work too.
Thought of that one but didn't know how zen it was.
>Maybe you could explain the particulars of your application, but I'm
unclear
>why receiving a beam causes a problem. If receiving a beam causes a
problem,
>there are probably other things that will also.
Not true, Beam receiving will interrupt an app for possibly extended periods
of time. I can't think of any other operation outside of your app that will
suspend your app for more than a few ticks. (I've already taken care of low
battery warnings while allowing the critical alarm to shut down the unit.
And alarms are no problem)
If I'm receiving data that is order sensitive, I don't want an IR source
interrupting during that process. (and another Palm may not be the source,
just pass your Palm near a laptop with HotSync running and sniffing the IR
port)
The actual Beam receive process doesn't cause a problem, just the fact that
my app becomes suspended could damage irreplaceable data. Like I stated
before, my intention is not to disable beaming, just postpone it for a few
ticks.
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palm.com/devzone/mailinglists.html