.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Flex
Sent: Thursday, January 15, 2004 4:54 PM
To: Palm Developer Forum
Subject: Re: Different behavior - Emulator vs. M105
As mentioned in the docs - at some devices a nilevent will not be fired.
How do you
Hmm... that leads to... remove EvtSetNull... function and in the
AppEventLoop where the EvtGetEvent(...,evtWaitForever(or similar))
change to EvtGetEvent(...,SysTicksPerSecond()/3(for example)). This way
you are sure a nilevent will be fired every 1/3 of the second... If
there are other events it
I have gotten a simple app running on my emulator that updates 6 fields on
the screen (via a nilEvent/'timer'). When I run this on my desktop, the
emulator functions as expected and the numbers scroll through indefinitely.
However, when I download the app to my M105, I no longer see numbers in
As mentioned in the docs - at some devices a nilevent will not be fired.
How do you do the waiting code and the evtgetevent?
Jim White wrote:
I have gotten a simple app running on my emulator that updates 6 fields on
the screen (via a nilEvent/'timer'). When I run this on my desktop, the
