Skip to main content

MIDlet states on startup

1 reply [Last post]
Joined: 2007-07-18

I've been reading a bit about MIDlet states and the AMS.

According to what I've read, on starting a MIDlet, it is moved into the Paused state, and then into an Active state by the AMS calling startApp().

My question is, why does it do it in this particular order on the first startup? Why does the MIDlet not just execute the startApp() method and move straight into an Active state without having been in a Paused one?


Reply viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.
Joined: 2004-03-04

I guess that is mainly for symmetry reasons. The transition active->paused->active can happen at any later point once the MIDlet is execution so the MIDlet needs to implement these transitions anyway if it requires any special operations going into or coming out of the paused state.

-- Terrence