I am entering the fray late here and haven't read the earlier messages on
this but I thought I might have something to add. One suggestion is to use
a power or other hard button to cancel the loop. That seems to be a better
solution since it doesn't have to handle an event, per say, it can
constantly monitor for the hard button tap (it also makes the code tighter,
since all you have to do is display a dialog telling the user what to do,
monitor for the button select, and close the dialog).
One other thought on recursive: depending on your situation and what you are
doing within, be careful of stack overflow. Palm, in the early days, said
don't use recursion because of stack issues. That may be different now, but
the stack space is still pretty small.
Just a couple of thought. I hope I added something new and apologize if I
didn't.
Elia
-----Original Message-----
From: Ron Nicholson [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, October 12, 1999 11:22 PM
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Subject: Re: Breaking out of loop with button press
But would your real event loop be calling MenuHandleEvent...
This is actually an important question. Although all recursive
computations
