That's too bad ... I am having similar symptoms
(that were cleared up by checking "save behind",
thanks for that!).
Question 1: why would one want (or not want)
"save behind" checked? It seems that the default
for constructor is not checked, but that is the mode
that causes these symptoms.
Question 2: I don't -think- my code is calling FrmGotoForm
more than once the way Bradly's was ... so what else
could be going on that would cause these symptoms?
--
-Richard M. Hartman
[EMAIL PROTECTED]
186,000 mi/sec: not just a good idea, it's the LAW!
Bradly J. Barton wrote in message <5547@palm-dev-forum>...
>
>ROFL .. Ok, now I feel dumb and I've broadcasted it for the world to see..
>as I was reading my own post that was sent to the board, I saw the
problem...
>
>>static void ChangeCurrentView(Word newView)
>>{
>> CurrentView = newView;
>> FrmGotoForm(CurrentView);
>>}
>>
>>DWord PilotMain(Word cmd, Ptr cmdPBP, Word launchFlags)
>>{
>> Err err;
>> if (cmd == sysAppLaunchCmdNormalLaunch)
>> {
>> err = StartApplication();
>> if (err) return err;
>> FrmGotoForm(CurrentView);
>> EventLoop();
>> }
>> return 0;
>>}
>>
>>static Err StartApplication(void)
>>{
>> ChangeCurrentView(MainForm);
>> return 0;
>>}
>
>StartApplication is, in essence, setting CurrentView and doing a
>FrmGotoForm for Main .. then the PilotMain function calls FrmGotoForm on
>CurrentView for a second time... omitting this call in PilotMain made the
>problem go away.. I guess OS3.5 just isn't as forgiving as the previous
>OS's :)
>
>----------
>Bradly J. Barton - [EMAIL PROTECTED]
>Jenies Technologies Incorporated
>(972) 602-1835
>JTI.net
>PalmInHand.com
>
>
>
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palm.com/devzone/mailinglists.html