Menu
▾
▴
#68 Handle exceptions more gracefully
Since CB is taking big steps towards 1.0, it's time to keep an eye on robustness and user experience.
When unhandled exceptions occur, CB is usually terminated. On all devices I tested with, CB's title bar remains visible above windows' start menu and by some reason even hardware keys to activate the start menu don't work anymore. In fact, the whole device is rendered unusable after abnormal terminations of CB and has to be restarted.
If anybody has an idea why this is happening and/or how this problem can be solved, please don't hesitate to let CB handle exceptions more gacefully.
noone willing to work on this?
Just a reminder. I still think this issue is a show stopper for 1.0, since it leads to loss of unsaved data in 3rd party applications and to loss of a lot of user's time.
From my point of view this is still the biggest show stopper for 1.0 - I experienced several losses of data recently and suggest this issue being discussed on the next online conference.