blocks|key|2234858|text|对于高帧率，您将希望使用Direct2D或OpenGL呈现，而不是内置的编辑窗口类。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2234859|如果你不需要高帧率，只需要高吞吐量，你可以执行InvalidateRect，只在收到PAINT消息时更改文本。Windows将限制向您发送WM_PAINT的速率。或者使用计时器。这样，您只需将新值存储在内部变量中，并在获得绘图或计时器回调时，将其从interval变量移动到编辑控件。|offset|length|style|CODE|2234860|entityMap^0|0|N|E|1X|8|0^^$0|@$1|2|3|4|5|6|7|J|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|K|8|@$D|L|E|M|F|G]|$D|N|E|O|F|G]]|9|@]|A|$]]|$1|H|3|-4|5|6|7|P|8|@]|9|@]|A|$]]]|I|$]]

For high frame rates, you'll want to use Direct2D or OpenGL rendering, not the built-in EDIT window class.

If you don't need a high frame rate, just high throughput, you could do <code>InvalidateRect</code> and only change the text when you get a PAINT message. Windows will limit the rate it sends you <code>WM_PAINT</code>. Or use a timer. In this way you just store the new value in an internal variable and when you get a paint or timer callback, move it from the interval variable to the EDIT control.

blocks|key|2234873|text|我已经通过维护上一次窗口更新的时间戳来解决这类问题。然后，我会阻止另一次更新，除非经过了一定的时间。十分之一秒的时间对我来说似乎相当不错。性能明显提高，更新看起来仍然很顺利。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2234874|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|$]]

I have gotten around this type of problem by maintaining a timestamp of the last window update. I would then prevent another update unless a certain amount of time had passed. 1/10th of a second seemed to work pretty well for me. Performance improved noticeably and updates still looked smooth.

blocks|key|2225610|text|这段代码中有相当多的内容。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2225611|SetWindowText本身似乎不太可能是速度较慢的部分。让我们一块一块地把它拆开，看看时间会往哪里去。(确定的唯一方法是分析，但我不能为您这样做，所以我正在寻找可能性。这取决于您的衡量。)|2225612|SetWindowText(GetDlgItem(+gHWnd,+IDC_PACKETID+),+
++++++++++++++(LPSTR)std::to_string(long+long(NC->mPacketNum)).c_str());|code-block|syntax|javascript|2225613|2225614|+GetDlgItem调用可能正在发送消息以遍历gHWnd的子窗口。如果有很多孩子，如果IDC_PACKETID不是第一个孩子，这可能需要一些时间。考虑计算一次并缓存结果。除非你销毁控件并创建一个新的，否则HWND不会改变。|ordered-list-item|2225615|你正在用ASCII字符串调用SetWindowText。(为什么要对结果进行强制转换？尤其是，你为什么要抛弃常识呢？)如果您使用的是现代版本的Windows，那么您的ASCII字符串将被动态转换为宽字符串，这可能涉及到额外的动态内存管理。您可以调用SetWindowTextW+(请注意W后缀)并直接使用std::to_wstring计算宽字符串。根据std::to_wstring的实现细节，这可能会更快。|2225616|窗口真的是一个编辑控件吗？如果你要以30-50+Hz的频率改变它，你似乎不太可能需要一个功能齐全的编辑控件。您可以使用静态文本控件来代替吗？它可能有一个更简单更快的implementation.|2225617|Is+NC->mPacketNum将在很长一段时间内正确对齐？如果不对齐，这可能会对性能产生不利影响。看看你是否能保证对齐。|2225618|2225619|entityMap^0|0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|V|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|W|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|X|8|@]|9|@]|A|$G|H]]|$1|I|3|-4|5|6|7|Y|8|@]|9|@]|A|$]]|$1|J|3|K|5|L|7|Z|8|@]|9|@]|A|$]]|$1|M|3|N|5|L|7|10|8|@]|9|@]|A|$]]|$1|O|3|P|5|L|7|11|8|@]|9|@]|A|$]]|$1|Q|3|R|5|L|7|12|8|@]|9|@]|A|$]]|$1|S|3|-4|5|6|7|13|8|@]|9|@]|A|$]]|$1|T|3|-4|5|6|7|14|8|@]|9|@]|A|$]]]|U|$]]

There is quite a lot going on in that code.

It seems unlikely that SetWindowText itself is the slow part. Let's take it apart piece by piece and see where the time may be going. (The only way to know for sure is to profile, but I can't do that for you, so I'm looking at possibilities. It's up to you to measure.)

<pre><code>SetWindowText(GetDlgItem( gHWnd, IDC_PACKETID ), 
 (LPSTR)std::to_string(long long(NC-&gt;mPacketNum)).c_str());
</code></pre>

<ol>
<li>The GetDlgItem call might be sending messages to walk the child windows of gHWnd. If there are many children, and if IDC_PACKETID is not one of the first ones, this could cost some time. Consider computing this once and caching the result. The HWND won't change unless you destroy the control and create a new one.</li>
<li>You're calling SetWindowText with an ASCII string. (Why are you casting the result? And, especially, why are you casting away the const-ness?) If you're on a modern version of Windows, then your ASCII string is being converted to a wide string on the fly, which could involve additional dynamic memory management. You could call SetWindowTextW (note the W suffix) and compute the wide string directly with std::to_wstring. Depending on the implementation details of std::to_wstring, this could be faster.</li>
<li>Is the window really an edit control? If you're changing it at 30-50 Hz, it seems unlikely that you need a full-fledged edit control. Can you use a static text control instead? It might have a simpler and faster implementation.</li>
<li>Is NC->mPacketNum going to be properly aligned for a long long? If it's not aligned, this can adversely affect performance. See if you can guarantee alignment.</li>
</ol>

I've got a simple application where I'm reading some internal variables and posting them to EditControl's on a menu.

Here is a code snippet

<pre><code>case 0:
 SetWindowText(GetDlgItem( gHWnd, IDC_PACKETID ), 
 (LPSTR)std::to_string(long long(NC-&gt;mPacketNum)).c_str());
 break;
</code></pre>

So there's a lot going on there. I'm just trying to convert a number to something that can be shown in the edit dialog. This is so slow, that I can drop from 50Hz to about 30Hz just by entering this section.

Any ideas to speed this up significantly?

SetWindowText Slow, Win32 C++

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

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

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

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

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

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

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

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

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

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

我有一个简单的应用程序，我正在读取一些内部变量，并将它们发布到菜单上的EditControl。下面是一个代码片段case 0:        SetWindowText(GetDlgItem( gHWnd, IDC_PACKETID ),                      (LPSTR)std::to_stri...

问SetWindowText Slow，Win32 C++
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问SetWindowText Slow，Win32 C++EN