IValueConverter的异步实现

时间:2013-02-21 13:44:50

标签: c# windows-runtime async-await c#-5.0 winrt-async

如果是我想在IValueConverter中触发的异步方法。

是否有更好的等待,然后通过调用结果属性强制它同步?

public async Task<object> Convert(object value, Type targetType, object parameter, string language)
{
    StorageFile file = value as StorageFile;

    if (file != null)
    {
        var image = ImageEx.ImageFromFile(file).Result;
        return image;
    }
    else
    {
        throw new InvalidOperationException("invalid parameter");
    }
}

2 个答案:

答案 0 :(得分:39)

由于某些原因,您可能不想拨打Task.Result

首先,我在我的博客上详细解释you can deadlock,除非您的async代码是使用ConfigureAwait编写的。其次,您可能不希望(同步)阻止您的UI;最好在从磁盘读取时暂时显示“正在加载...”或空白图像,并在读取完成时进行更新。

所以,就个人而言,我会将这部分视为我的ViewModel,而不是值转换器。我有一篇博客文章描述了一些databinding-friendly ways to do asynchronous initialization。那将是我的第一选择。让值转换器启动异步后台操作感觉不对。

但是,如果你已经考虑过你的设计并且真的认为你需要一个异步值转换器,那么你必须有点创造性。值转换器的问题是它们具有是同步的:数据绑定从数据上下文开始,评估路径,然后调用值转换。只有数据上下文和路径支持更改通知。

因此,您必须在数据上下文中使用(同步)值转换器将原始值转换为数据绑定友好的Task类似对象,然后您的属性绑定只使用其中一个属性Task - 像获取结果的对象一样。

这是我的意思的一个例子:

<TextBox Text="" Name="Input"/>
<TextBlock DataContext="{Binding ElementName=Input, Path=Text, Converter={local:MyAsyncValueConverter}}"
           Text="{Binding Path=Result}"/>

TextBox只是一个输入框。 TextBlock首先将自己的DataContext设置为通过“异步”转换器运行它的TextBox输入文本。 TextBlock.Text设置为该转换器的Result

转换器非常简单:

public class MyAsyncValueConverter : MarkupExtension, IValueConverter
{
    public object Convert(object value, Type targetType, object parameter, System.Globalization.CultureInfo culture)
    {
        var val = (string)value;
        var task = Task.Run(async () =>
        {
            await Task.Delay(5000);
            return val + " done!";
        });
        return new TaskCompletionNotifier<string>(task);
    }

    public object ConvertBack(object value, Type targetType, object parameter, System.Globalization.CultureInfo culture)
    {
        return null;
    }

    public override object ProvideValue(IServiceProvider serviceProvider)
    {
        return this;
    }
}

转换器首先启动异步操作等待5秒,然后添加“完成!”到输入字符串的末尾。转换器的结果不能只是普通的Task,因为Task没有实现IPropertyNotifyChanged,所以我使用的是将在我{的下一个版本中的类型{3}}。它看起来像这样(本例简化; AsyncEx library):

// Watches a task and raises property-changed notifications when the task completes.
public sealed class TaskCompletionNotifier<TResult> : INotifyPropertyChanged
{
    public TaskCompletionNotifier(Task<TResult> task)
    {
        Task = task;
        if (!task.IsCompleted)
        {
            var scheduler = (SynchronizationContext.Current == null) ? TaskScheduler.Current : TaskScheduler.FromCurrentSynchronizationContext();
            task.ContinueWith(t =>
            {
                var propertyChanged = PropertyChanged;
                if (propertyChanged != null)
                {
                    propertyChanged(this, new PropertyChangedEventArgs("IsCompleted"));
                    if (t.IsCanceled)
                    {
                        propertyChanged(this, new PropertyChangedEventArgs("IsCanceled"));
                    }
                    else if (t.IsFaulted)
                    {
                        propertyChanged(this, new PropertyChangedEventArgs("IsFaulted"));
                        propertyChanged(this, new PropertyChangedEventArgs("ErrorMessage"));
                    }
                    else
                    {
                        propertyChanged(this, new PropertyChangedEventArgs("IsSuccessfullyCompleted"));
                        propertyChanged(this, new PropertyChangedEventArgs("Result"));
                    }
                }
            },
            CancellationToken.None,
            TaskContinuationOptions.ExecuteSynchronously,
            scheduler);
        }
    }

    // Gets the task being watched. This property never changes and is never <c>null</c>.
    public Task<TResult> Task { get; private set; }

    Task ITaskCompletionNotifier.Task
    {
        get { return Task; }
    }

    // Gets the result of the task. Returns the default value of TResult if the task has not completed successfully.
    public TResult Result { get { return (Task.Status == TaskStatus.RanToCompletion) ? Task.Result : default(TResult); } }

    // Gets whether the task has completed.
    public bool IsCompleted { get { return Task.IsCompleted; } }

    // Gets whether the task has completed successfully.
    public bool IsSuccessfullyCompleted { get { return Task.Status == TaskStatus.RanToCompletion; } }

    // Gets whether the task has been canceled.
    public bool IsCanceled { get { return Task.IsCanceled; } }

    // Gets whether the task has faulted.
    public bool IsFaulted { get { return Task.IsFaulted; } }

    // Gets the error message for the original faulting exception for the task. Returns <c>null</c> if the task is not faulted.
    public string ErrorMessage { get { return (InnerException == null) ? null : InnerException.Message; } }

    public event PropertyChangedEventHandler PropertyChanged;
}

通过将这些部分放在一起,我们创建了一个异步数据上下文,它是值转换器的结果。数据绑定友好的Task包装器将使用默认结果(通常为null0),直到Task完成。所以包装器的ResultTask.Result完全不同:它不会同步阻塞,也没有死锁的危险。

但重申:我选择将异步逻辑放入ViewModel而不是值转换器。

答案 1 :(得分:0)

另一种方法是使您自己的控件支持异步源或数据。

这是图片示例

    public class AsyncSourceCachedImage : CachedImage
{
    public static BindableProperty AsyncSourceProperty = BindableProperty.Create(nameof(AsyncSource), typeof(Task<Xamarin.Forms.ImageSource>), typeof(AsyncSourceSvgCachedImage), null, propertyChanged: SourceAsyncPropertyChanged);

    public Task<Xamarin.Forms.ImageSource> AsyncSource
    {
        get { return (Task<Xamarin.Forms.ImageSource>)GetValue(AsyncSourceProperty); }
        set { SetValue(AsyncSourceProperty, value); }
    }

    private static async void SourceAsyncPropertyChanged(BindableObject bindable, object oldColor, object newColor)
    {
        var view = bindable as AsyncSourceCachedImage;
        var taskForImageSource = newColor as Task<Xamarin.Forms.ImageSource>;

        if (taskForImageSource != null)
        {
            var awaitedImageSource = await taskForImageSource;

            view.Source = awaitedImageSource;
        }
    }
}

此外,您可以在图像上实施加载活动指示器,直到任务完成。