Hi,
Yeah i know may be the code is not very nice :(
But the way i am handling all the forms is like this :
Boolean XXX(EventPtr eventP)
{
Boolean handled = false;
switch (eventP->eType)
{
case frmOpenEvent:
<< my code >>
break;
case scanDecodeEvent:
<< my code >>
break;
case frmCloseEvent:
<< my code >>
break;
}
return handled;
}
So effectively evenif after executing frmCloseEvent
break statement return handled is executed which is
false. So i think it serves that purpose what you were
suggesting.
Please suggest if i am wrong somewhere.
Thanks again.
--- Aaron Ardiri <[EMAIL PROTECTED]> wrote:
> > Like Aaron said, the problem is that you end up
> returning "true"
> > after handling the frmCloseEvent -- you need to
> return "false" to
> > allow the OS to finish closing the form (or you
> can read the OS
> > source and find everything the OS does, and
> duplicate the work
> > yourself, and keep your app updated for all OS
> versions and all
> > devices -- but it's much better to just return
> "false" and allow
> > the OS to do its work properly).
>
> you saw a return true? :) i gave up trying to read
> the code when
> i saw 3-4 return statements, a few breaks, and, code
> that wasn't
> very pleasing to the eye :)
>
> when he does break, we dont know if he returns true
> or false. so,
> we dont have all the pieces to the puzzle to solve
> it do we? :P
>
> ---
> Aaron Ardiri
> [EMAIL PROTECTED]
> CEO - CTO
> +46 70 656 1143
> Mobile Wizardry
> http://www.mobilewizardry.com/
>
> --
> For information on using the Palm Developer Forums,
> or to unsubscribe, please see
http://www.palmos.com/dev/support/forums/
________________________________________________________________________
Missed your favourite TV serial last night? Try the new, Yahoo! TV.
visit http://in.tv.yahoo.com
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palmos.com/dev/support/forums/
