Just a couple of additional comments...
> I have had problems with using nil events as pose creates extra
> nil events causing problems, my method appears to work fine so far.
POSe is an emulator not the real device....
> The solution is not to fire off your own event on every nilEvent.
> Look at the # of sys ticks since the last nilEvent or the system
> time to determine if you should proceed.
Agree'd and as I suggested. My suggestion was to use the nilevent
sent at a predertermined time in the eventloop to fire the custom
event described. Which should still be a case on nilevent with
a quick test on time.
What other way is there to fire off a custom event?
evtgetevent (timetowaitforevent) ?
either you wait for an event (now/tomorrow/next month)
or you send a nil at whatever time you specify.
is there a evtgetevent(until xtimepasses send my custom event) ?
Be certain to turn OFF the device with your program running
and turn it back on after a few minutes to check that you are
still polling time correctly. just an FYI. but I guess your
not using the ticks just seconds.
Why cannot an evtgetevent(systickspersec/2) work...
you'll get a nil every 30 seconds... then in your handler
have a case on nilevent. run it to a func that tests current time
form a saved time (sysgetseconds) and if a minute has passed
do your thing. simple elegant etc. etc...
One thing I have learned is the best code ends up being the
simple solution on the palm.
just a few cent's
Good Luck!
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palmos.com/dev/tech/support/forums/
