Peter Chin wrote:
I display a clock within my application that works both on the Treo 650 and in
POSE.
The application contains its own event stack, separate from that belonging to
the system. The main event loop calls the application's event handler whenever
a nilEvent is received. This event handler is independent of any form (so I've
never had to figure out whether or not a form would receive a nilEvent). Before
checking for events in its own stack, the handler checks to see if the clock
has changed. When it does, it updates the clock field in the form displayed. I
simply ensure that the clock field has the same id across all forms.
Perhaps not the most elegant of solutions but it works.
Alas, in my case, this elapsed time counter is user-started and stopped
with a button, and the form that displays this chronometer-like feature
(used to estimate the depth of a pit in a cave based on the fall time of
a rock) has other controls too, so it would make litle sense to drop the
form's event handler and transfer all this handling over to the main
event loop.
--
Luc Le Blanc
--
For information on using the PalmSource Developer Forums, or to unsubscribe,
please see http://www.palmos.com/dev/support/forums/
