03-31-2010 05:58 AM
Hi,
the below code work perfect in 8900 but the same it doesn't work in blackberry 9700.BScrenn i had pushed before and then i called iAScreen and it also shown correctly but later i called below code i got the iAScreen even though i pop it .
UiApplication.getUiApplication().invokeLater (new Runnable() {
public void run()
{
getApplication().requestForeground();
UiApplication.getUiApplication().popScreen(iAScree n);
//method to be called.
BAcreen.invalidate();
}
}); Please reply if anybody has faced the same problem before,
thanks,
Ganesh
03-31-2010 06:39 AM
Have you confirmed that iAScreen is referenced correctly in this code?
Is this code running in a listener or in your own application?
03-31-2010 07:35 AM
Hi peter, Thanks for your reply.it is in my own app.i have confirmed the referenced as well.see,if the code works perfect in 8900 and then it should also work in 9700.
03-31-2010 07:52 AM
"code works perfect in 8900 and then it should also work in 9700"
Mostly. But I have had Ui code that worked on older releases that didn't work on new ones, because in fact I had coded something incorrectly that the older releases could cope with, but the newer release objected to (quite rightly). I recoded it correctly and it worked on all releases.
Are you testing this code on the device or on the Simulator? What OS Levels are involved here?
One point of confusion for me is the use of
getApplication().
and
UiApplication.getUiApplication().
Are these actually getting different Applications?
04-01-2010 02:07 AM - edited 04-01-2010 02:08 AM
Hi,
thanks for reply once again.
I am testing the app on this v5.0.0.461 (Plataforma 5.2.0.42) blackberry 9700. i got a lot of issue on this
like i am not able to hide the application using " UiApplication.getUiApplication().requestBackground
Please anybody has faced above issue on os v5.0.0.461 .Please help me out.
Thanks,
ganesh
04-01-2010 03:51 AM
Can we just confirm that the issues you are seeing are happening to one OS Level release on the 9700?
If so, raise this with Issue Tracker, that sounds like a bug.