进展如何<T>不同于Action<T>?(C#)

问题描述

我一直在使用Progress<T>，想知道是否可以将其替换为Action<T>.

I've been using Progress<T> and wondered if it can be replaced by Action<T>.

在下面的代码中，使用它们中的每一个来报告进度，即 ReportWithProgress() 或 ReportWithAction()，对我没有任何明显的影响.progressBar1 是如何增加的，字符串是如何写在输出窗口上的，它们看起来都一样.

In the code below, using each of them for reporting progress, i.e. ReportWithProgress() or ReportWithAction(), didn't make any noticeable difference to me. How progressBar1 increased, how the strings were written on the output window, they seemed the same.

// WinForm application with progressBar1

private void HeavyIO()
{
    Thread.Sleep(20); // assume heavy IO
}

private async Task ReportWithProgress()
{
    IProgress<int> p = new Progress<int>(i => progressBar1.Value = i);

    for (int i = 0; i <= 100; i++)
    {
        await Task.Run(() => HeavyIO()); 
        Console.WriteLine("Progress : " + i);
        p.Report(i);
    }
}

private async Task ReportWithAction()
{
    var a = new Action<int>(i => progressBar1.Value = i);

    for (int i = 0; i <= 100; i++)
    {
        await Task.Run(() => HeavyIO());
        Console.WriteLine("Action : " + i);
        a(i);
    }
} 

但是 Progress<T> 不能是轮子的再发明.实施它应该是有原因的.谷歌搜索c# Progress vs Action"并没有给我太多帮助.Progress 与 Action 有何不同?

But Progress<T> can't be a reinvention of the wheel. There should be a reason why it was implemented. Googling "c# Progress vs Action" didn't give me much help. How is Progress different from Action?

推荐答案

从不同的线程调用 progressBar1.Value = i 会导致可怕的 跨线程操作无效"异常.另一方面，Progress 类将事件分派到 同步上下文在构建时刻捕获:

Calling progressBar1.Value = i from a different thread results in the dreaded "cross-thread operation not valid" exception. The Progress class, on the other hand, dispatches the event to the synchronization context captured in the moment of construction:

// simplified code, check reference source for actual code

void IProgress<T>.Report(T value)
{
    // post the processing to the captured sync context
    m_synchronizationContext.Post(InvokeHandlers, value);
}

private void InvokeHandlers(object state)
{
    // invoke the handler passed through the constructor
    m_handler?.Invoke((T)state);

    // invoke the ProgressChanged event handler
    ProgressChanged?.Invoke(this, (T)state);
}

这可确保对进度条、标签和其他 UI 元素的所有更新都在(一个且唯一的)GUI 线程上完成.

This ensures that all updates to progress bars, labels and other UI elements are done on a (one and only) GUI thread.

因此，只有在 UI 线程上调用的方法内实例化后台线程的 Progress 类outside 才有意义:

So, it only makes sense to instantiate the Progress class outside of the background thread, inside a method which is called on a UI thread:

void Button_Click(object sender, EventArgs e)
{
    // since this is a UI event, instantiating the Progress class
    // here will capture the UI thread context
    var progress = new Progress<int>(i => progressBar1.Value = i);

    // pass this instance to the background task
    Task.Run(() => ReportWithProgress(progress));
}

async Task ReportWithProgress(IProgress<int> p)
{
    for (int i = 0; i <= 100; i++)
    {
        await Task.Run(() => HeavyIO());
        Console.WriteLine("Progress : " + i);
        p.Report(i);
    }
}

这篇关于进展如何<T>不同于Action<T>?(C#)的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持跟版网！