Add support to the Smartphone platform for Asynchronous Dialogs (standardAskAsync, customAskAsync) like the PlayBook platform has. This provides a consistent API between PlayBook and Smartphone and will allow for emulation in Ripple (not in scope of this issue).
Use the old style callback approach in order to reduce scope of this fix, unless we have a stable platform already for the event based approach.
This would mean that we mark the customAsk() and standardAsk() functions as "marked for deprecation" in the API reference and in the code.
Need to update docs as well.
Due to Smartphone API restrictions, the current optional "settings" parameter for the Async dialogs will NOT be supported in the Smartphone WebWorks SDK. If it is provided, it should be gracefully ignored at runtime.
I have created an java application which mimics WebWorks customAskAsync and as expected the dialog does not exit when the back button is pressed.
I am currently trying to find a workaround and so far no luck.
But I will continue looking into finding a workaround.
I believe this is the same issue that is going on with the Back button with the new v2.3 navmode that is in the process of being fixed
Good News, it looks I have found a workaround for back button for custom dialog issue and currently I have set it so that we would return the default choice indicated by the developer, is this we would want?
Correction in my last comment, the default choice is currently set to first choice in the list of choices.
StandardAsk returns blackberry.ui.dialog.C_CANCEL (which is -1) constant value.
If you mean return the same value as standardAsk when the hardware back button is pressed, then it can be done.
Included in 2.3.1 release