01-29-2012 04:33 PM
Hi Maadani, the reason I find this frustrating, is because of the debugging ability of the BB tools. When The error occurs, it just freezes. Now, like I did say earlier, on the simulator, you really have to click on different buttons and menus at a haphazard rate for about 40secs to generate the same error. But on the device, a single or maximum one click on the menu freezes the app. No trace, no warning, NOTHING. The error occurs mainly when I try to use the LWUIT menu on the storm
01-31-2012 07:42 PM
Simon, is there a way of getting a stack trace or some way of knowing where the overflow occurs. As it is, The app just freezes. no clue nothing. Even the debugger is just as perplexed as me. wandering what happened
02-01-2012 02:52 AM
02-21-2012 08:04 AM - edited 02-21-2012 08:05 AM
Sorry for the "me-too" post...
BUT maybe some more info can help.
Getting the same problem, no LWUIT, nothing fancy, just purely native BB UI code.
I do have one custom Field subclass, since that was the only way to get what I needed,with a side-dish of performance.
Now, just before I dig into some more debugging: some thoughts:
Any case, IF I get my problem solved, I vow solemnly I will post my solution here - it MIGHT be applicable, Unlike the parrot (don't worry about the parrot - it's not applicable)
02-21-2012 08:11 AM
02-21-2012 08:14 AM
02-21-2012 08:19 AM
02-21-2012 09:02 AM
02-21-2012 09:23 AM
I suggest to start with the simple things...
Since it's a UI issue, start with the obvious methods taken on the UI thread (layout, sublayout, etc') and search from there the objects you create and the method that you are calling.
Since you have one field, I would start with creating a new application with one screen and only your field.
This will let you see if the problem is with your field or not.
Note: the fact that the test application will not crash does not mean that your field is working fine. You should check with the profiler that your code is indeed working correctly.
Hope that helps,