peter_strange wrote:
Just out of interest, does CONSUME_CLICK actually resolve the issue in your test case? If it does, that may well give us a hint to the real problem.
I do think you are hitting a Storm related issue rather than an OS 5.0 related issue. The Storm is different in its processing of events, to the extent I try not to support it if I can get away with it....
Try another OS 5.0 device to see if the problem is present there also.
I won't have time to test this code myself till much later.
Yes it does solve it, seams on the storm the click events aren't consumed unless they're explictly told to be consumed meaning they get passed down the chain eventually reaching the OS where it attempts to display the contextual menu, which it can't because the Dialog is the screen on the top of the stack not the extended MainScreen
