The DialogService controls all dialogs and this is why its events fire for all dialogs. If you want to execute code after a specific dialog is closed you can use the Then event of the Open dialog action in Radzen.
I just deleted a previous loooong post here ... because ... I got multiple dialogs to work, as follows:
I initially did not notice that DialogService.OpenAsync returns the result - SO, there is no need for OnClose event handlers ... you can just continue working on the result after the awaited call returns.
Once I eliminated the OnClose event handlers all together, nested dialogs seem to work fine?
So it appears to me that DialogService.Close(...) just closes the top-most dialog, while the underlying one remains open and ok.
Thus, regarding:
[korchev]
Hi @kim,
The DialogService controls all dialogs and this is why its events fire for all dialogs. If you want to execute code after a specific dialog is closed you can use the Then event of the Open dialog action in Radzen.
Perhaps we can get by without any event handlers, i.e. if you want to execute code after a specific dialog closes, the you await the call to open it and assign the result in the same call, and then continue to execute in the same method ... works for me, am I missing anything?