Resources | developer.brewmp.com Resources | developer.brewmp.com

Developer

resources

Critical events

When implementing an applet, handle only the events your applet might want to process. Some events can be ignored, such as in a game that uses only up, down, left and right keys as input, an event corresponding to a key press of keys 0-9 can be ignored. Critical events received by an applet can't be ignored, regardless of the state of the applet. Pay careful attention to receiving all the critical events in any given state of the applet. Some events are not sent to the applet unless it specifically indicates that it wants such notifications. Applets must register for these notification events either permanently in the MIF, or dynamically using ISHELL_RegisterNotify().

The following events should be handled. The applet is closed if TRUE is not returned.

  • EVT_APP_START
  • EVT_APP_START_BACKGROUND
  • EVT_APP_SUSPEND
  • EVT_APP_RESUME
  • EVT_APP_STOP