08-05-2008 05:56 AM
The 10 sec interval in the application is too short, as the next event would refresh the screen when you
unlock the keyboard.
If you increase it to say 60 sec, and then try, you will see the effect.
You can see what the screen looks like by looking at the hang.JPG file on my iDisk
08-05-2008 09:55 AM
Minor point, probably not relevant, and this is from memory so might be complete tosh....
I've had problems using priority 1 because my screen was maintained over the top of a real BB screen - from memory one of the request notification screens - and this actually caused a deadlock, can't remember how. So I tend to use 99 now, i.e.
queueStatus(globalScreen, 99, true);
08-05-2008 01:02 PM
Thanks Peter, I tried using 99 but had the same issue when testing in the simulator.
Did not try on an actual device, but my guess is it would behave the same on the device as well....
08-07-2008 03:00 PM