On January 30, 2004 07:55 am, Fabian Cenedese wrote:
I think I already found the (apparent) difference in the events, the (not) hanging in the OnLButtonDown. I need to find out why it doesn't stay in there and if it's in listview, message, events...
The mouse tracking in listview happens in the LISTVIEW_TrackMouse() function, which seems correct. It is getting called from only one place (in LISTVIEW_LButtonDown()) so a few print statements there would be nice to see that (1) it is being called, and (2) that it doesn't exit prematurely.
In this case a PE build of the comctl32 would be priceless: you could just replace the native comctl32 DLL on a real Windows installation with our own implementation, and see if the problem persists. Is so, the error is in our comctl32 DLL. If not, it is in the lower layers (message, events, etc.).
In fact, a PE build of the comctl32 would be so useful that I'm a bit surprised nobody attempted it thus far... We should offer a full PE build on SourceForge, together with the other downloads. Any takers?