Robert Baruch wrote:
Yeah, that's the sysAppLaunchCmdSyncNotify launch code. So at least
I know I'm on the right track. Unfortunately, I can't even pop up a
little dialog from that launch command because the device will then
crash :( Not very useful for debugging :( :(
In situations like that, I do this kind of thing:
SndPlaySystemSound (sndInfo);
SysTaskDelay (SysTicksPerSecond());
SndPlaySystemSound (sndInfo);
SysTaskDelay (SysTicksPerSecond());
SndPlaySystemSound (sndInfo);
SysTaskDelay (SysTicksPerSecond());
SndPlaySystemSound (sndInfo);
SysTaskDelay (3 * SysTicksPerSecond());
Then some other place, I might do this:
SndPlaySystemSound (sndInfo);
SysTaskDelay (SysTicksPerSecond());
SndPlaySystemSound (sndClick);
SysTaskDelay (SysTicksPerSecond());
SndPlaySystemSound (sndClick);
SysTaskDelay (SysTicksPerSecond());
SndPlaySystemSound (sndInfo);
SysTaskDelay (3 * SysTicksPerSecond());
Or this:
SndPlaySystemSound (sndInfo);
SysTaskDelay (2 * SysTicksPerSecond());
SndPlaySystemSound (sndInfo);
SysTaskDelay (SysTicksPerSecond());
SndPlaySystemSound (sndInfo);
SysTaskDelay (3 * SysTicksPerSecond());
By varying the beeps and the clicks and the timing, you can come up
with a number of patterns that are easy to recognize. Plus you provide
amusement for your co-workers when they see you listening intently to
the Palm like it's whispering the answers to you or something.
- Logan
--
For information on using the PalmSource Developer Forums, or to unsubscribe,
please see http://www.palmos.com/dev/support/forums/
