我有一个设想。(Windows Forms, c#, .NET)
There is a main form which hosts some user control.
The user control does some heavy data operation, such that if I directly call the UserControl_Load method the UI become nonresponsive for the duration for load method execution.
To overcome this I load data on different thread (trying to change existing code as little as I can)
I used a background worker thread which will be loading the data and when done will notify the application that it has done its work.
Now came a real problem. All the UI (main form and its child usercontrols) was created on the primary main thread. In the LOAD method of the usercontrol I'm fetching data based on the values of some control (like textbox) on userControl.
伪代码看起来像这样:
代码1
UserContrl1_LoadDataMethod()
{
if (textbox1.text == "MyName") // This gives exception
{
//Load data corresponding to "MyName".
//Populate a globale variable List<string> which will be binded to grid at some later stage.
}
}
它给出的例外是
跨线程操作无效:从创建该控件的线程以外的线程访问的控件。
为了了解更多关于这一点,我做了一些谷歌搜索,并提出了一个建议,如使用以下代码
代码2
UserContrl1_LoadDataMethod()
{
if (InvokeRequired) // Line #1
{
this.Invoke(new MethodInvoker(UserContrl1_LoadDataMethod));
return;
}
if (textbox1.text == "MyName") // Now it won't give an exception
{
//Load data correspondin to "MyName"
//Populate a globale variable List<string> which will be binded to grid at some later stage
}
}
但我似乎还是回到了原点。再次申请
变得反应迟钝。这似乎是由于第1行if条件的执行。加载任务再次由父线程完成,而不是由我生成的第三个线程完成。
我不知道我认为这是对还是错。
我如何解决这个问题,以及执行第1行if块的效果是什么?
情况是这样的:我想根据控件的值将数据加载到全局变量中。我不想改变子线程中控件的值。我不会从子线程中做。
因此只有访问值,才能从数据库中获取相应的数据。
UI中的线程模型
为了理解基本概念,请阅读UI应用程序中的线程模型(旧的VB链接在这里)。该链接导航到描述WPF线程模型的页面。但是,Windows窗体利用了相同的思想。
UI线程
只有一个线程(UI线程)被允许访问System.Windows.Forms.Control及其子类成员。
试图从不同的线程访问System.Windows.Forms.Control的成员会导致跨线程异常。
因为只有一个线程,所以所有的UI操作都作为工作项进入该线程:
如果UI线程没有工作,那么就存在空闲间隙,可以由与UI无关的计算使用。
为了使用上述间隙,请使用System.Windows.Forms.Control.Invoke或System.Windows.Forms.Control.BeginInvoke方法:
BeginInvoke和Invoke方法
The computing overhead of method being invoked should be small as well as computing overhead of event handler methods because the UI thread is used there - the same that is responsible for handling user input. Regardless if this is System.Windows.Forms.Control.Invoke or System.Windows.Forms.Control.BeginInvoke.
To perform computing expensive operation always use separate thread. Since .NET 2.0 BackgroundWorker is dedicated to performing computing expensive operations in Windows Forms. However in new solutions you should use the async-await pattern as described here.
Use System.Windows.Forms.Control.Invoke or System.Windows.Forms.Control.BeginInvoke methods only to update a user interface. If you use them for heavy computations, your application will block:
调用
System.Windows.Forms.Control.Invoke导致单独的线程等待,直到调用的方法完成:
BeginInvoke
System.Windows.Forms.Control.BeginInvoke不会导致单独的线程等待被调用的方法完成:
代码的解决方案
阅读问题的答案如何更新GUI从另一个线程在c# ?
对于c# 5.0和。net 4.5,推荐的解决方案在这里。
UI中的线程模型
为了理解基本概念,请阅读UI应用程序中的线程模型(旧的VB链接在这里)。该链接导航到描述WPF线程模型的页面。但是,Windows窗体利用了相同的思想。
UI线程
只有一个线程(UI线程)被允许访问System.Windows.Forms.Control及其子类成员。
试图从不同的线程访问System.Windows.Forms.Control的成员会导致跨线程异常。
因为只有一个线程,所以所有的UI操作都作为工作项进入该线程:
如果UI线程没有工作,那么就存在空闲间隙,可以由与UI无关的计算使用。
为了使用上述间隙,请使用System.Windows.Forms.Control.Invoke或System.Windows.Forms.Control.BeginInvoke方法:
BeginInvoke和Invoke方法
The computing overhead of method being invoked should be small as well as computing overhead of event handler methods because the UI thread is used there - the same that is responsible for handling user input. Regardless if this is System.Windows.Forms.Control.Invoke or System.Windows.Forms.Control.BeginInvoke.
To perform computing expensive operation always use separate thread. Since .NET 2.0 BackgroundWorker is dedicated to performing computing expensive operations in Windows Forms. However in new solutions you should use the async-await pattern as described here.
Use System.Windows.Forms.Control.Invoke or System.Windows.Forms.Control.BeginInvoke methods only to update a user interface. If you use them for heavy computations, your application will block:
调用
System.Windows.Forms.Control.Invoke导致单独的线程等待,直到调用的方法完成:
BeginInvoke
System.Windows.Forms.Control.BeginInvoke不会导致单独的线程等待被调用的方法完成:
代码的解决方案
阅读问题的答案如何更新GUI从另一个线程在c# ?
对于c# 5.0和。net 4.5,推荐的解决方案在这里。