Why does WinRT not queue MessageDialogAsync and WebAuthenticationBroker calls itself?


  • I had this situation today that while the user can click on the surface and invoke the WAB, an error in the database layer of the app can occur in the background. When this happens I display a MessageDialog. Yet, when the WAB window is already open, you cannot display a MessageDialog and vice versa.

    Why didn't the WinRT team not think of that, in an async application? Why do I now have to remember application wide, if a modal dialog (WAB, MessageDialog, FilePicker) is already open end queue up MessageDialog, WAB, FilePicker calls to until the open dialog closes?

    Friday, March 15, 2013 4:10 PM