为什么 DataGridView 上的 DoubleBuffered 属性默认为 false 以及为什么它受到保护？

发布于 2024-07-07 20:14:59 字数 286 浏览 7 评论 0原文

我们遇到了 DataGridViews 的性能问题，重绘速度非常慢，并找到了解决方案此处创建派生类型并在控件上启用双缓冲。（派生类型是必要的，因为 DoubleBuffered 属性受到保护）

将 DoubleBuffered 属性设置为 true 似乎没有任何缺点。

原文

分享到QQ

分享到微博

如果你对这篇内容有疑问，欢迎到本站社区发帖提问参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。

发布评论

需要登录才能够评论，你可以免费注册一个本站的账号。

池予 2024-07-14 20:14:59

我认为最好的解决方案：

typeof(DataGridView).InvokeMember(
   "DoubleBuffered", 
   BindingFlags.NonPublic | BindingFlags.Instance | BindingFlags.SetProperty,
   null, 
   myDataGridViewObject, 
   new object[] { true });

在这里找到

I think its best solution:

typeof(DataGridView).InvokeMember(
   "DoubleBuffered", 
   BindingFlags.NonPublic | BindingFlags.Instance | BindingFlags.SetProperty,
   null, 
   myDataGridViewObject, 
   new object[] { true });

found here

回复收藏 0 原文

浮光之海 2024-07-14 20:14:59

它受到保护是因为 DGV 继承了 Control 的属性。并且 Control.DoubleBuffered 受到保护。这是有道理的，因为每个派生控件都应该自行决定打开它。而且控制用户随意打开或关闭它是没有意义的。 DGV 设计师决定放弃。

他们可能做出这一决定的原因之一是双缓冲实际上会使绘制速度变慢。渲染缓冲区位图的额外步骤会花费时间。它只是人眼看起来更快，您会观察到位图突然出现。您无法看到绘制位图所需的时间。除非其他控件需要绘制并且它们在 DGV 之后轮到它们，否则它是相当明显的。

您看到的是首先绘制的窗体，控件所在的位置有孔。这些孔有白色背景。当您使用 TransparencyKey 或 Opacity 属性时为黑色。然后每个控件都会获取 Paint 事件，并将漏洞一一填充。这种效果也被用户视为闪烁，尽管它与 DoubleBuffered 解决的闪烁是不同类型的。当背景为黑色时尤其明显。

解决这个问题需要的是整个窗体及其所有控件都是双缓冲的。这在 Windows 窗体中不可用。然而，Windows XP 和更高版本实际上支持这一点，他们称之为“合成”。将此代码复制/粘贴到表单类中的任意位置：

protected override CreateParams CreateParams {
    get {
        CreateParams cp = base.CreateParams;
        cp.ExStyle |= 0x02000000;  // Turn on WS_EX_COMPOSITED
        return cp;
    }
}

It is protected because DGV inherits the property from Control. And Control.DoubleBuffered is protected. Which makes sense because each derived control should decide for itself to turn that on. And it doesn't make sense for the control user to arbitrarily turn it on or off. The DGV designers decided for off.

One reason they might have decided that is that double buffering actually makes painting slower. The extra step to render the buffer bitmap costs time. It just looks faster to the human eye, you observe the bitmap suddenly appearing. You can't see the time it takes to draw into the bitmap. Unless other controls need to be painted and they get their turn after the DGV, then it is quite visible.

What you see is the form getting drawn first, with holes where the controls go. Those holes have a white background. Black when you use the TransparencyKey or Opacity property. Each control then gets the Paint event and the holes are filled one-by-one. That effect is perceived as flicker too by the user, although it is a different kind of flicker from the one that DoubleBuffered solves. It is especially noticeable when the background is black.

What's needed to solve this problem is that the entire form, with all its controls, is double-buffered. That's not available in Windows Forms. However, Windows XP and later actually support this, they called it "compositing". Copy/paste this code anywhere in the form class:

protected override CreateParams CreateParams {
    get {
        CreateParams cp = base.CreateParams;
        cp.ExStyle |= 0x02000000;  // Turn on WS_EX_COMPOSITED
        return cp;
    }
}

回复收藏 0 原文