ListView painting (was Re: Mouse up vs Mouse click)

Fabian Cenedese Cenedese at
Thu Jan 29 07:55:01 CST 2004

At 08:27 29.01.2004 -0500, Dimitrie O. Paun wrote:
>On January 29, 2004 08:08 am, Fabian Cenedese wrote:
>> Understandable. Any hints how I could continue? Where to look at?
>I don't think I understand this bit. Care to explain it again?
>  "So for me it looks like this: When I click in a cell it gets invalidated
>   and painted selected. But if the cell is not in the first row the first
>   column (or the whole line) gets invalidated and repainted too, therefore
>   erasing the already painted selection."

Another idea: When a line changes it is completely invalidated and
repainted without any selection. The the new cell is painted again
with selection. So what if these two events are in wrong order? My
cell gets selected and immediately loses it again. And that's maybe
what happens as "it" (main thread?) doesn't wait in the OnLButtonDown
as it does for the first column cells.
Of course it's not just that simple as I made a test with a simple
ownerdrawn listcontrol which of course worked. So it must be more
in my app that interferes. Could it be that the listview is inside a ocx?
Different event handling?

bye  Fabi

More information about the wine-devel mailing list