C# – Preventing color bleeding with StateImageList on TreeView

cnettreeviewwinforms

Does anyone have a solution for the color bleeding when using a StateImageList with a Windows Forms TreeView?

Using the same ImageList with assigned to the TreeView's ImageList property, results in correct rendering as can be seen by the following image.

24 bit

The state images are left, normal images are right. All images are sourced from the same ImageList instance.

Update:

I converted the images to 16 color indexed palette. Seems it does not like that either. Its a bit better, but still far from acceptable.

4 bit

Best Answer

The documentation on the .ColorDepth property of the .StateImageList states:

In the .NET Framework version 1.1 or later, the default is Depth8Bit.

It looks like this 'default' is not allowed to be changed. Well, you can change it, but it doesn't do any good.

Looking at the code in Reflector, when the StateImageList property of the the TreeView is set, a new image list is created internally. This image list uses the default value for color depth. And since you cannot change the color depth after creating the imagelist, this pretty much guarantees that the StateImageList can only be displayed at the default color depth.

EDIT: I think I've figured out what's going on here. I have been playing around with images like your shaded circles at varying color depths. Basically, when I take a decent image and convert it to 4-bit color, I get results that look exactly like the images from the StateImageList. Despite the '8-bit' note in the documentation, it appears that the StateImageList is still using 4-bit color depth (the old, old 16-color standard) as the default.

It is only when I use 4-bit images to start with in the imagelist, that I get no changes between the display of the imagelist and stateimagelist.

alt text http://www.freeimagehosting.net/uploads/74873abc94.png

I created this image for the imagelist using the old Windows 16-color palette. It looks absolutely terrible, but it didn't change in the stateimagelist.

Related Solutions

C# – How to save application settings in a Windows Forms application

If you work with Visual Studio then it is pretty easy to get persistable settings. Right click on the project in Solution Explorer and choose Properties. Select the Settings tab and click on the hyperlink if settings doesn't exist.

Use the Settings tab to create application settings. Visual Studio creates the files Settings.settings and Settings.Designer.settings that contain the singleton class Settings inherited from ApplicationSettingsBase. You can access this class from your code to read/write application settings:

Properties.Settings.Default["SomeProperty"] = "Some Value";
Properties.Settings.Default.Save(); // Saves settings in application configuration file

This technique is applicable both for console, Windows Forms, and other project types.

Note that you need to set the scope property of your settings. If you select Application scope then Settings.Default.<your property> will be read-only.

Reference: How To: Write User Settings at Run Time with C# - Microsoft Docs

C# – Func delegate with no return type

All Func delegates return something; all the Action delegates return void.

Func<TResult> takes no arguments and returns TResult:

public delegate TResult Func<TResult>()

Action<T> takes one argument and does not return a value:

public delegate void Action<T>(T obj)

Action is the simplest, 'bare' delegate:

public delegate void Action()

There's also Func<TArg1, TResult> and Action<TArg1, TArg2> (and others up to 16 arguments). All of these (except for Action<T>) are new to .NET 3.5 (defined in System.Core).

Best Answer

Related Solutions

C# – How to save application settings in a Windows Forms application

C# – Func delegate with no return type

Related Topic