03-12-2010 12:26 PM
I chose an item out of a select , query my sqlite DB and return the data to a div on screen. Simple enough and works 99% of the time.
However, that 1% pops up. My widget seems to freeze. I can no longer interact with anything on screen. I can't back out of my widget by hitting the back or the end call button. The only way I can escape from my widget is holding the menu button to open the application switcher. At this point, I can't open my widget again by clicking on the icon. Nothing happens.
Finally, (10 or so minutes later...) I get an "Uncaught exception: Application emitwidget (220) is not responding; process terminated"
The reason this is odd, After getting the error, I can open my widget again and it starts a new instance. I can go into my select and chose the same item that caused it to freeze and everything will work without a problem.
Please enlighten as to what might be going on here.
03-12-2010 01:22 PM
Is this only happening when you are using the focus based navigation mode in your markup?
03-12-2010 01:59 PM - edited 03-12-2010 02:04 PM
Tim,
I haven't had the issue with the Rim navigation mode off... only with it on.
03-12-2010 03:29 PM
I wonder if it is a similar focus problem like you had with the push data where you needed to explicitly call focus back on the select.
03-12-2010 03:51 PM
I don't believe so. The same code works the rest of the time and just after I was able to get back into my widget (post RIM error dialog).
Also, I do a blackberry.focus.setFocus(....) at the end of the function that is called on the selection of an item.
01-10-2011 07:40 AM
Hello,
I have the same probleme with OS6.
What is the trick ?
01-11-2011 03:00 AM
In my case, blackberry.focus.setFocus is the problem.
When I remove it, it works with OS6
I don't have the problem with OS5
01-12-2011 12:06 AM
I too have been experiencing this problem with my app for OS 6. However, even when I have disabled the navigation mode in the config.xml, I at times receive this error when queing results from my db and displaying it rows of a table.
01-16-2011 01:27 AM
Have you been able to find a solution for this? Has turning off the navigation mode solved this problem?
01-16-2011 09:20 PM
This seems really strange. Does anyone have a chunk of code that will duplicate this problem consistently? We can run it through its paces.