Well I just got drilled & grilled over this again..
I'll start with...
I don't generally SPLASH anymore...
This is a snip from an old PILOT program
and PLEASE FORGIVE ME!
As I extinguish my smoldering fanny....
You're kidding, right?
You really don't see the hole in your "
if (TimeTks == TimGetTicks())" logic below?
-----------------------
--> I Didn't say I did'nt see the problem
-----------------------
If a system action stops the app from executing for some
period of time during your while loop
(e.g. interrupts become disabled,
background thread suspends app thread,
tick counter gets reset, etc.) it may never exit the loop.
-----------------------
--> Not like I know squat but
WHAT BACKGROUND THREAD!
the palm is a single threaded OS
when MY app runs it's got full attention?
(am I missing something?!)
Tapping anything will just pile up the
event queue! <no?>
-----------------------
The correct test is "if (TimeTks < TimGetTicks())"
and use a UInt32 for the TimeTks variable.
You should also test for overflow in your initialization
of TimeTks, though the only thing that would happen if
TimGetTicks() + 110 overflowed a UInt32 is that the
splash screen would go away immediately.
-----------------------
--> Excellent and thank-you
I always prefer constructive replies
-----------------------
BTW, this approach may annoy your users,
because they can't tap the screen or press
a button to dismiss the splash screen.
-----------------------
--> Ain't that the point?
It's not at all Zen-of-Palm...
Please no more ZEN stuff!
Zen of Unix... Zen of Windoze... Zen of Porsche...
I do however thank you for the responce
It serves to remind myself of my seriously
lacking K&R/Stroustrup skills!
HowY
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palmos.com/dev/tech/support/forums/
