I am curious if anyone has any other experience with WPF ItemsControls (ListView, ListBox, etc.) and hopefully some tips for me. :)
Just an ordinary ListBox, say ... 300-500 elements (with or without data binding, did not make an obvious difference), with virtualization turned on, when I click and drag the thumb up and down (scroll up / down), I notice that my processor (3.4ghz) runs up to about 90%. And while everything is reasonably responsive, he feels a bit indecisive. I noticed this with most ItemsControls, and I wonder if this is my computer or if such CPU usage is a justifiable compromise for a rich interface? These are only ItemsControls that have this behavior; I did not find ScrollViewer on its own to be slow.
Setting it ScrollViewer.CanContentScrollto false (which makes virtualization pointless) has accelerated scrolling. However, the selection of items became very slow, which I would not have expected. The resize / layout also suffered a lot, but this was expected.
Compared to the win32 list, which uses <3% cpu when scrolling through the same number of items, I tend to ask these questions (I'm trying to get away from win32, though :).
Is it just because I'm using XP (sp3, with .NET 4.0)?
Is this my video card (NVidia GeForce 7300 GS pcie)?
Or what do I feel normal?
I don’t have any means right now to test on another (faster) machine, so I rely on the experience of others who would have some kind of idea. It seems to me that WPF was only compatible with XP and aimed at Vista and higher.
, WPF, , VS/Blend, , WPF?
.:)