This color picker behaves just like the ones in the "Appearance" tab of the Display properties dialog. Here is how the button looks like:
The picker has a "most recently used colors" feature. If you click on the "Other" button and select a color that is not in the current set, the least recently used color gets replaced.
It is very easy to use.
How to include in your project
- Copy ColorBtn.cpp and ColorBtn.h into your project directory.
- Copy ColorBtn.rc into your res directory.
- Add this line to your rc2 file:
- Add ColorBtn.cpp to your project.
How to use
- Create a button on your dialog. Mark it as "Owner Draw".
- Declare a variable in your dialog class, like this:
- At OnInitDialog, call SubclassDlgItem, like this:
colorbtn.SubclassDlgItem(IDC_BUTTON,this); // Use your button ID here
- Repeat the process for each button you want. You'll end up with as many member variables as buttons.
You can set and read the selected color using the "currentcolor" member variable.
How to make your color table persistent
When the buttons start up, the color table is set to the standard 20 static colors. After using them for a while, those colors might have changed. If you want to preserve the modified color table, follow one of the these procedures.
In a single application, all buttons share a single color table. Because of this, you don't have to do this for each button. Just use the static version of the desired function once (e.g. call CColorBtn::Load()).
There are two ways to make your color table persistent. Application-wise and Document-wise.
Application-wise means that you store the color table in the registry. This way, all documents share the same color table. CColorBtn provides two static functions to do this:
Gets the colors from the registry
Stores the colors in the registry
These functions require that you call SetRegistryKey() before using them.
Document-wise means that you store the color table in a file along with the rest of the document data. This way, each document has its own color table. Note that even in Document-wise fashion, all the buttons you use in a single application share their color table (this was at the artists' petition, I don't know, they seem to like it this way). CColorBtn provides two functions to do this:
- Serialize(CArchive &ar)
Serializes the color table, you call this in your document's Serialize() function.
Resets the color table back to the standard 20 static colors. You call this in your document's OnNewDocument() function.