blocks|key|485294|text|从你的帖子中并不清楚你到底想做什么，但听起来你应该把你的模型/服务调用放在一个单独的线程上(通过后台工作者或异步委托)，并在完成时使用模型/服务调用的回调来通知UI。然后，您的UI线程可以做一些繁忙的事情，比如显示进度条，但不会变得无响应。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|485295|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

It's not clear from your post exactly what you are trying to do, but it sounds like you should put your model/service calls on a separate thread (via Background worker or async delegate) and use a callback from the model/service call to notify the UI when it's done. Your UI thread can then do busy things, like show a progress bar, but not become unresponsive.

blocks|key|2397945|text|您的问题似乎可以用Threading解决。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|2397946|在WPF中，您可以执行以下操作：|2397947|Thread+t+=+new+Thread((ThreadStart)delegate()+{
+++while+(true)+{
++++++Thread.sleep(500);
++++++if+(c.hasChanged())
++++++++++Dispatcher.Invoke((Action)delegate()+{updateData();});
+++}

}).Start();|code-block|syntax|javascript|2397948|在WinForms中|2397949|Thread+t+=+new+Thread((ThreadStart)delegate()+{
+++while+(true)+{
++++++Thread.sleep(500);
++++++//+this+must+derive+from+Control
++++++if+(c.hasChanged())
++++++++++this.Invoke((Action)delegate()+{updateData();});
+++}

}).Start();|2397950|可能缺少Invoke的参数(在调用UI线程上执行代码时需要它)，但是我是从我的大脑中编写的，所以没有智能感知|2397951|在.NET+4中，您可以使用TaskFactory.StartNew而不是自己创建线程。在.Net+<=+4中，您可以使用线程的TreadPool。然而，我记得你需要立即运行它，因为你希望它尽快在那里检查，而线程池不能保证这一点(它可能已经满了，但不太可能：-)。只是不要做一些愚蠢的事情，比如在一个循环中产生更多的它们！|2397952|在线程内部，你应该放一个像这样的检查|2397953|while+(!Closing)|2397954|这样线程就可以在你需要它的时候结束，而不必求助于像t.Abort();这样的坏东西，当退出时，将关闭设置为true，并执行一个t.Join()来关闭检查线程。|style|CODE|2397955|编辑：|2397956|我忘了说闭合应该是一个布尔属性或VOLATILE布尔值，而不是一个简单的布尔值，因为您不能确保线程能够完成(当然，如果您要关闭应用程序，它会完成，但让它们按您的意愿完成是一个很好的实践)。volatile关键字旨在防止(伪)编译器对假定变量值不能更改的代码应用任何优化|2397957|entityMap|0|LINK|mutability|MUTABLE|url|http://msdn.microsoft.com/en-us/library/aa645740%2528v=vs.71%2529.aspx|1|http://msdn.microsoft.com/en-us/library/zyzhdc6b.aspx|2|http://msdn.microsoft.com/en-us/library/dd321439.aspx|3|http://msdn.microsoft.com/en-us/library/system.threading.threadpool.aspx|4|http://msdn.microsoft.com/en-us/library/x13ttww7%2528v=vs.71%2529.aspx^0|9|9|0|0|0|0|0|0|4|6|1|0|E|K|2|1S|9|3|0|0|0|P|A|1R|8|0|0|G|8|4|0^^$0|@$1|2|3|4|5|6|7|1K|8|@]|9|@$A|1L|B|1M|1|1N]]|C|$]]|$1|D|3|E|5|6|7|1O|8|@]|9|@]|C|$]]|$1|F|3|G|5|H|7|1P|8|@]|9|@]|C|$I|J]]|$1|K|3|L|5|6|7|1Q|8|@]|9|@]|C|$]]|$1|M|3|N|5|H|7|1R|8|@]|9|@]|C|$I|J]]|$1|O|3|P|5|6|7|1S|8|@]|9|@$A|1T|B|1U|1|1V]]|C|$]]|$1|Q|3|R|5|6|7|1W|8|@]|9|@$A|1X|B|1Y|1|1Z]|$A|20|B|21|1|22]]|C|$]]|$1|S|3|T|5|6|7|23|8|@]|9|@]|C|$]]|$1|U|3|V|5|H|7|24|8|@]|9|@]|C|$I|J]]|$1|W|3|X|5|6|7|25|8|@$A|26|B|27|Y|Z]|$A|28|B|29|Y|Z]]|9|@]|C|$]]|$1|10|3|11|5|6|7|2A|8|@]|9|@]|C|$]]|$1|12|3|13|5|6|7|2B|8|@]|9|@$A|2C|B|2D|1|2E]]|C|$]]|$1|14|3|-4|5|6|7|2F|8|@]|9|@]|C|$]]]|15|$16|$5|17|18|19|C|$1A|1B]]|1C|$5|17|18|19|C|$1A|1D]]|1E|$5|17|18|19|C|$1A|1F]]|1G|$5|17|18|19|C|$1A|1H]]|1I|$5|17|18|19|C|$1A|1J]]]]

Your problem seems to be solvable with <a href="http://msdn.microsoft.com/en-us/library/aa645740%28v=vs.71%29.aspx" rel="nofollow">Threading</a>.

In WPF you can do:

<pre><code>Thread t = new Thread((ThreadStart)delegate() {
 while (true) {
 Thread.sleep(500);
 if (c.hasChanged())
 Dispatcher.Invoke((Action)delegate() {updateData();});
 }

}).Start();
</code></pre>

In WinForms

<pre><code>Thread t = new Thread((ThreadStart)delegate() {
 while (true) {
 Thread.sleep(500);
 // this must derive from Control
 if (c.hasChanged())
 this.Invoke((Action)delegate() {updateData();});
 }

}).Start();
</code></pre>

There may be missing parameters to <a href="http://msdn.microsoft.com/en-us/library/zyzhdc6b.aspx" rel="nofollow">Invoke</a> (which is needed to execute the code on the calling UI thread) but I'm writing this from my brain so no intellisense at disposal :D

In .NET 4 you can use <a href="http://msdn.microsoft.com/en-us/library/dd321439.aspx" rel="nofollow">TaskFactory.StartNew</a> instead of spawning a thread by yourself.
In .Net &lt;= 4, you could use the <a href="http://msdn.microsoft.com/en-us/library/system.threading.threadpool.aspx" rel="nofollow">TreadPool</a> for the thread.
However I recall you need this to be run at once because you expect it to be there checking as soon as possible and the thread pool won't assure you that (it could be already full, but not very likely:-).
Just don't do silly things like spawning more of them in a loop!

And inside the thread you should put a check like 

<pre><code>while (!Closing)
</code></pre>

so that the thread can finish when you need it without having to resort to bad things like <code>t.Abort();</code>
An when exiting put the Closing to true and do a <code>t.Join()</code> to close the checker thread.

EDIT:

I forgot to say that the Closing should be a bool property or a <a href="http://msdn.microsoft.com/en-us/library/x13ttww7%28v=vs.71%29.aspx" rel="nofollow">VOLATILE</a> boolean, not a simple boolean, because you won't be ensured that the thread could ever finish (well it would in case you are closing the application, but it is good practice to make them finish by your will). the volatile keyword is intended to prevent the (pseudo)compiler from applying any optimizations on the code that assume values of variables cannot change

blocks|key|2409696|text|如果从图形用户界面轮询，请使用(WinForms)计时器。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2409697|如果这是某种后台进程，那么您的睡眠()可能是较小的坏处。|2409698|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

If you are polling from a GUI, use a (WinForms) Timer. 

If this is some kind of background process, your Sleep() may be the lesser evil.

blocks|key|2397989|text|显式的忙碌等待是不好的，必须尽可能避免。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2397990|如果无法避免，则使用观察者设计模式构建应用程序，并将感兴趣的对象注册到由线程支持的执行轮询的对象。|2397991|这样你就有了一个干净的设计，把丑陋的东西限制在一个地方。|2397992|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|I|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|J|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|G|$]]

Explicit busy waiting is evil and must be avoided whenever possible.

If you cannot avoid it, then build your application using the Observer design pattern and register the interested objects to an object which performs the polling, backed by a thread.

That way you have a clean design, confining the ugly stuff in just one place.

How do you implement busy waiting in a not total inefficient way? I am facing the issue that I can load the data of my model only in a pull manner, which means I have to invoke getXYZ() methods in a continuous way.

This has to happen not fast enough for user interaction, but fast enought, that when a state in the GUI is changed, the model can be noticed and the new state is received by the getXYZ() methods.

My approach simply be:

<pre><code>while (c.hasChanged()) {
 Thread.sleep(500);
}
updateData();
</code></pre>

Are there better mechanisms?

Busy waiting in C#

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

你如何以一种不是完全低效的方式实现忙碌等待？我面临的问题是，我只能以拉入的方式加载模型的数据，这意味着我必须以连续的方式调用getXYZ()方法。对于用户交互，这必须发生得不够快，但是足够快，当图形用户界面中的状态改变时，模型可以被注意到，并且getXYZ()方法接收新的状态。我的方法很简单：while (c.hasC...

问在C#中忙于等待
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问在C#中忙于等待EN