Hello,

I am using a ListView derived class in VirtualMode to display millions of
lines (Details view). DoubleBuffering is on.
The underlying data is frequently updated. The ListView is informed of the
update by setting the VirtualListSize property.

There are three scenarios:
1. The ListView always scrolls to the last message. => Everything ok, no
flicker.
2. A row is selected and visible, no scrolling occurs but the underlying
data is still being updated. => Everything OK, no flicker, only the scroll
bar is sligtly moving as expected.
3. A row is selected but the selected row was scrolled outside the visible
area of the ListView and is no longer visible. => Ugly flickering occurs.

I examinded the third scenario and found, that each time I set the
VirtualListSize, the ListView is processing TWO WM_PAINT messages .
In the first, it paints the selected row and the rows adjacent to the
selection (which shouldn't be painted).
The second WMPaint then paints the rows, which are expected to be painted.

I don't know, why there are 2 WM_PAINT messages and how to prevent the first
one, which isn't necessarry and is responsible for the flicker.

I appreciate any idea hot to solve this problem.

Regards

Ulrich Proeller