notifyPaused() not necessarily called....

"Darryl Pierce" <mcpierce@gmail.com> wrote in message
news:E468e.87404$wo1.58259@bignews6.bellsouth.net...
> Anton Spaans wrote: 
>
> Of course it is! It's in the specification: MIDlet.notifyPaused() does
> exactly what he's asking.

But what if your phone does not call this 'notifyPaused()' callback method?
Instead, your phone may be very low on resources and decides to close your
J2ME program all together (e.g. when an incoming call must be handled)

I agree; *if* your midlet's notifyPaused() is called, then you can handle
some code to clean up some resources to go into 'minimized' state.

>
> --
> Darryl L. Pierce <mcpierce@gmail.com>
> Visit my homepage: http://mcpierce.multiply.com
> "By doubting we come to inquiry, through inquiry truth." - Peter Abelard

Anton Spaans wrote: 
>
> But what if your phone does not call this 'notifyPaused()' callback method?[/color
]

Then the handset's not up to the specification, since it's supposed to
do just that.

> Instead, your phone may be very low on resources and decides to close your
> J2ME program all together (e.g. when an incoming call must be handled)

Then in that case the phone must call MIDlet.destroyApp(boolean).

> I agree; *if* your midlet's notifyPaused() is called,

It's MIDlet.pauseApp(). MIDlet.notifyPaused() is how the application
tells the handset that it wants to be paused.

--
Darryl L. Pierce <mcpierce@gmail.com>
Visit my homepage: http://mcpierce.multiply.com
"By doubting we come to inquiry, through inquiry truth." - Peter Abelard