Hello, We are stumped with a peculiar behavior. I appreciate any pointers.
The application has 2 alarm procedures (one for the background mode and the other one for the foreground). When the application exits, we unregister the foreground alarm proc (third param 0) and register for background alarm proc. In the background, the background alarm proc gets called. It registers for next timer (background proc). Now, the foreground alarm gets called which is strange! I have stopped the foreground alarm proc (confirmed that it is being called) while exiting. The workarounds we tried were looking for the SysCurApp.. in the foreground proc and not call the code when it is not the present application. However, we show some UI in the background by opening some resources and hence, this cannot be done. The alarmP->ref reference number is also not reflecting correctly. It is showing the ref number of foreground proc though I registered for background proc. How does the OS manage the alarm code? Does it wait for the next nilEvent and then process the pending requests? My code resets the foreground proc and then sets the alarm for background. Thanks and happy holidays! - Raj -- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
