Don't mean to beat a dead horse with a stick! but when
I use "FrmPopupForm" and subsequently "FrmReturnToForm(0)"
The FrmUpdate Even is fired... OK I get it ...but what I
don't get.. is the form "I return to," is updated and displayed;
but then emulator still goes back through the AppEventLoop even
I'm having issues returning from a form called by using FrmPopupForm. Here's
snippits of my code:
In my main form menu handler:
case EditPrefs:
FrmPopupForm(PrefsForm);
handled = true;
break;
In my application event handler:
switch ( uiFormId ) {
Thanks to anyone considering slapping-me-upside-the-head.
I figured out what I was doing wrong... I had called api FrmReturnToForm(0)
which would cause it to return to the form that called
the FrmPopupForm command... however the problem is I had forms stacked.. i.e
(9500),(9501) and (9502) respec
Your code looks just like mine (pretty standard,
as you said), except that I tend to use
FrmReturnToForm(0);
instead of
FrmReturnToForm(MainForm);
(not sure if that could make a difference, though).
Oliver
__
Do you Yahoo!?
Yahoo! Mail Plus
> FrmReturnToForm(0);
When I first looked at that I went "Gah!", as I always thought it required the
ID of a form... RTFM, and I disover otherwise. Spiffy.
> FrmReturnToForm(MainForm);
> (not sure if that could make a difference, though).
It didn't. What -did- make a difference is replaci
It didn't. What -did- make a difference is replacing FrmPopupForm and
FrmReturnToForm with FrmGotoForm. Now it works without -any- problems. What
a stupid git problem this is. Is there any reason I should stick with
Popup/Return instead of going with Goto now? Will I melt if I stay with
goto
Ben,
> studying the way the OS creator's code works is
> a good way to see why to use a call and how to
> use it properly.
I am sure studying the internal workings of PalmOS
is very educational, but I don't think it should be
the (preferred) way for every developer to learn and
understand why,
At 07:36 2002-12-12 -0800, you wrote:
Ben,
> studying the way the OS creator's code works is
> a good way to see why to use a call and how to
> use it properly.
I am sure studying the internal workings of PalmOS
is very educational, but I don't think it should be
the (preferred) way for every d
> I wasn't saying that you should read the OS code,
> but instead read the sample apps included with the
> SDk.
Ooops. Yes. You're right, Ben. Sorry about that.
Note to self: don't post before 8am and before
consuming at least 1 cup of coffee.
Oliver
___
