Iterated a bit on the dialog view model design, it now uses the UI dispatcher to ensure the Close() method is invoked in the UI thread
This commit is contained in:
parent
e11922ae4f
commit
bedd49ce17
3 changed files with 29 additions and 24 deletions
|
|
@ -18,7 +18,6 @@ limitations under the License.
|
|||
#endregion // Apache License 2.0
|
||||
|
||||
using System;
|
||||
using System.Threading.Tasks;
|
||||
|
||||
using Nuclex.Avalonia.ViewModels;
|
||||
|
||||
|
|
@ -30,11 +29,6 @@ namespace Nuclex.Avalonie.ViewModels {
|
|||
/// <summary>Indicates that the view should close</summary>
|
||||
event EventHandler<DialogResultEventArgs> Submitted;
|
||||
|
||||
/// <summary>Indicates that the dialog should be closed</summary>
|
||||
/// <param name="dialogResult">Result the dialog should return</param>
|
||||
/// <returns>A task that finishes when the submit notification has been sent</returns>
|
||||
Task SubmitAsync(object? dialogResult = null);
|
||||
|
||||
}
|
||||
|
||||
} // namespace Nuclex.Avalonie.ViewModels
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue