12-02-2012 03:34 PM
Ok, then I have to mention that I am still building with Beta 3 (Build id: v201209241008) but device is upgraded to 1103.
12-02-2012 03:40 PM
The default C/OpenGL project will build and run fine on a dev alpha 1103, but an otherwise empty c++ project with that main.cpp will not. At least not on mine or the app submission people when built from my machine. This happens with tablet 2.1 or bb10 sdk, so it's probably the case with beta 3.
12-02-2012 10:14 PM
I'll risk to assume that application cannot properly function without window (and at the same time request screen events).
If you add this minimal init steps to your main():
screen_context_t screen_cxt;
screen_create_context(&screen_cxt, 0);
screen_window_t screen_win;
screen_create_window(&screen_win, screen_cxt);
int rect[4] = { 0, 0, 0, 0 };
screen_buffer_t screen_buf;
screen_create_window_buffers(screen_win, 1);
screen_get_window_property_pv(screen_win, SCREEN_PROPERTY_RENDER_BUFFERS, (void **)&screen_buf);
screen_post_window(screen_win, screen_buf, 1, rect, 0);
screen_flush_context(screen_cxt, SCREEN_WAIT_IDLE);
you'll get NAVIGATOR_EXIT (and other navigator events).
By the way this part also does not look nice:
} else if ((domain == navigator_get_domain())
&& (NAVIGATOR_EXIT == bps_event_get_code(event))) {
exit_application = 1;
}
Add break; after exit_application.
And final remark bps_get_event(&event, 0) will eat your CPU, in this particular example it is better to use bps_get_event(&event, -1))
12-14-2012 01:12 AM
12-14-2012 06:15 AM
There were a couple things.
1) 1103 has graphics bugs that are beyond my control. Some of these are fixed in the newest update.
2) In the update released yesterday, the os still has bugs. I figured out that if I draw an empty frame before doing anything else, things mostly work.
This cost me a lot of time, and possibly enough of a setback to not make the built for blackberry deadline. I did eventually get a rim engineer to admit the 1103 problems were not on my end.