Does anybody knows about problems on nilEvent ONLY on Tungsten C.
Simple code like :
EvtGetEvent(event, sysTicksPerSecond);
if (event.eType==nilEvent) UpdateDisplay();
does not work on T|C only ...
Any hints will be appreciated :-)
Bertrand Simon.
http://GPSpilot.com
--
For information
)
- Original Message -
From: Bertrand Simon [EMAIL PROTECTED]
Newsgroups: palm-dev-forum
To: Palm Developer Forum [EMAIL PROTECTED]
Sent: Friday, August 22, 2003 8:44 AM
Subject: Tungsten C and NilEvent problem ?
Does anybody knows about problems on nilEvent ONLY on Tungsten C.
Simple code like
Perhaps you should be checking how long it's been since your last time bar
drop, an don't do it again if it's been less than 250ms.
You should also look into UserEvents, and generate them where needed, rather
than relying on nilEvents, as these can be generated when you don't expect
them.
I have design an timing critical application that having a time bar dropping
every 250ms, so I used
EvtGetEvent(event, SysTicksPerSecond() / 4)
at my EventLoop routine and handled the dropping of time bar at nilEvent, it
works fine on PalmOS 3.x and 4.x, but having problem on Zire 71, the time
Aaron, thanks for help! It works perfect now!
Tony
Aaron Ardiri [EMAIL PROTECTED] wrote in message
news:[EMAIL PROTECTED]
I have design an timing critical application that having a time bar
dropping
every 250ms, so I used
EvtGetEvent(event, SysTicksPerSecond() / 4)
at my EventLoop
I have design an timing critical application that having a time bar dropping
every 250ms, so I used
EvtGetEvent(event, SysTicksPerSecond() / 4)
at my EventLoop routine and handled the dropping of time bar at nilEvent, it
works fine on PalmOS 3.x and 4.x, but having problem on Zire 71, the
