"Richard M. Hartman" wrote:
> Does posting an AppStopEvent instead of a silkscreen key press work ?
>
> --
> -Richard M. Hartman
> [EMAIL PROTECTED]
>
> 186,000 mi/sec: not just a good idea, it's the LAW!
>
> John Prinos wrote in message <25337@palm-dev-forum>...
> >
> >Hello all,
> >
> >BACKGROUND:
> >My app gets activated by tapping on its icon in the launcher app or by a
> >preset alarm.
> >
> >I don't use SysAppUISwitch to run the program from an alarm. I test for
> >the way the app was launched and go from there.
> >
> >Firstly, I know that 'exiting' an application is non-standard so I don't
> >want a philosophical discussion on the topic.
> >
> >The code to exit the app employs the old trick of adding a keyDownEvent
> >signifying the launch app. silkscreen pad:
> >
> > newEvent->eType = keyDownEvent;
> > newEvent->data.keyDown.chr = launchChr;
> > newEvent->data.keyDown.modifiers = commandKeyMask;
> > EvtAddEventToQueue (newEvent);
> >
> >
> >This works properly when the app was activated manually. I get to the
> >launcher app.
> >
> >
> >THE PROBLEM:
> >When it is activated through an alarm, exiting results with a blank
> >screen. I can't get to the launcher app by tapping on its silkscreen pad
> >directly. I have to tap on the calculator and then the launcher to get
> >it going.
> >
> >I've searched the literature to no avail. Has anyone seen this behavior
> >before?
> >
> >Thanks in advance,
> >
> >John
> >
> >
> >
>
> --
> For information on using the Palm Developer Forums, or to unsubscribe, please see
>http://www.palmos.com/dev/tech/support/forums/
That had the strange behavior of reactivating the application upon exit the first time
it was run. Afterwards it seemed to work ok.
The only other problem with that was that it would exit into other applications I had
just previously run.
John
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palmos.com/dev/tech/support/forums/
