OK, I'm using wxWidgets, but if you can tell me how to do it in win32 that would be much appreciated - I can probably find the relevent code with that info. I am doing a big refactor of some old code, and I'm using a list view as a texture browser. Now, my old code works fine, the highlight is in the true-colour style. My new code, which is almost a direct copy from the old, has a 256-colour style highlight. This is what I mean: Same image at 2x magnification: The one on the left is from the old version, the one on the right is the new version (as in - the icon, not the image - they are both the same image, increased in size for visibility). I'm using the same version of wxWidgets for both, and so I know it's not that. I vaugly remember having trouble getting it working correctly the last time around too. Unfortunatly I've left myself no comments on how it was done, and there is certianly no "Use the true-colour highlight" option that is obvious in the API. Any help is much appreciated. [Edited by - Andrew Russell on July 11, 2005 6:26:15 AM]

Additional note - SetUseBestVisuals(true) - has no effect. Both of the screenshots were taken with it in the code, and the sample where it also works in true-colour, it isn't.

*bump*

Just to be clear the images are the same - it is the icons that are different - they are screenshots from two different programs. I'll edit the post to make it clearer.


The icon on the left is what I'm aiming for. Basically - when it is selected, it takes on a blue tint. The icon on the right is what I currently have - the selection is indicated by setting certian pixels to normal dark blue using a pattern like this:

X X X X  X X X XX X X X  X X X X

In other words - correct one is using a true-colour method, the other is using the method in 256-colour mode (I'm not actually sure about the number of colours actually being used - but the highlight method is the same).

Although I'm using wxWidgets - if someone knows how to change between the two in win32, I can probably work out how to do it in wxWidgets (or hack it in).


I've been working to "fix" the broken version by copying in code from the working version. The code is now, pretty much identical to the working version in all the parts that should make a difference (the creation of the list view and image list, the loading of the images, manipulation of the list, etc), yet it's still broken. So it's something very obscure. I will now try to break the working version by copying various bits of the broken code over it to see what breaks it.

What color flags are you passing to the imagelist you use for the List Control?
I never noticed on the selection part (i usually use only report view), but i've had problems with color depths below 15/16 bit before.

My experience has been (with Win32) that List Views and other controls use the system palette... at least in older Windows OS's...

Not that that helps... but I'm not sure a Win32 List View's highlighting can be de-coupled from the display settings... at least automatically. (Could be wrong)... XP's themes I know nothing about, however.

You may have a "custom draw" operation staring you in the face :-/

Good luck... hope your API is out there

my_life:          nop          jmp my_life

Well, a custom-draw operation isn't an option. And anyway - I know it can be done without one.


On the subject of what is being passed to create the image list - to wxWidgets - nothing to do with colour depth.

Looking at the source code to wxWidgets itself, the code that creates an image list goes like this:



And wxDisplayDepth() does this:

ScreenHDC dc;return GetDeviceCaps(dc, PLANES) * GetDeviceCaps(dc, BITSPIXEL);

I will go in there with my debugger and see if the value is different.