Assuming that "ourMinVersion" is a #defined constant rather than a global,
the code looks OK except that if you arent planning to respond to the
sysAppLaunchCmdDisplayAlarm Launch Code, you should set cmdPBP->purgeAlarm
to true, not false. Hard to see how this could cause the symptoms you
describe though.
You could try confirming that nothing is turning off the alarm by dsplaying
the results of AlmGetAlarm() in AppStop.
Nick
-----Original Message-----
From: Greg McGraw [mailto:[EMAIL PROTECTED]]
Sent: Monday, 13 September 1999 3:49
To: [EMAIL PROTECTED]
Subject: sysAppLaunchCmdAlarmTriggered Not Received
An alarm is set in an active application under development. The alarm
functions as intended while the application remains active. However, if
the app is not active the alarm does not function. No alarm triggered
launch command gets to the application. It is as if by quiting the app
the alarm has been turned off.
Attached is a code fragment from the pilotmain, appstart, appstop &
alarmtriggered routines.
Thanks
Greg McGraw
static DWord XXXPilotMain(Word cmd, Ptr cmdPBP, Word launchFlags)
{
Err error;
error = RomVersionCompatible (ourMinVersion, launchFlags);
if (error) return (error);
...
