引用最近http://perseus.franklins.net/hansel分钟s_0166.pdf” rel=“nofollow noreferer”>Hansel分钟:

Ian Griffiths: ... There s the win32 cue which is an ordinary win32 message loop, and WPF pools messages off of that and puts them on it s own cue and then deal with it on it s own sweet time, partly because it wants to be able to reorder the events as they come in. It will prioritize certain things above input processing, for example, and that, by the way, is why you get the slightly bizarre repaint handling on resizing WPF applications, you may have noticed you get a little bit of blank space appearing temporarily when you resize a window it s because it s acknowledging the resize event before it actually really does anything with it and then the paints happen slightly out of sync with what s normally there. So there is a win32 message queue but it s not actually the main message queue in WPF and that‘s all sort of implementation details the dispatcher tries to hide as much about it as possible.

It seems relevant to your problem, though I m not aware of a complete solution. Maybe, you should try to change some Dispatcher priorities?

ault,我认为这可能与列入方框的虚拟化有关。 虚拟化使清单箱只能装载正在提供的那些信标要素。 清单箱帮助将StackPanel-PanelTemplate虚拟化。

因此,我的猜测似乎就是......尽量扩大窗口会推动名单箱产生更多的统一调查要素,而拖延会把黑色L 推到一边。

你可以消除虚拟化,并检查黑色分子是否仍然露面。 在实践中,虚拟化实际上是一种“好”的事物,而将其排除在外通常是坏的。