The autocomplete feature works nicely as long as you don't want to back up beyond the matching part of your typed string. For instance... if you type "Some Mean" ... it autocompletes with the "Some Meaningless".. which is the desired result. However, If you now try to backspace because you wanted to type "Some Meanie".. it will not let you. You have to select and delete the whole string in order to start fresh.
Until I am able to update this article, as an alternative, please visit this link http://www.codejock.com/ for the latest updates. My email address has changed also, please respond to firstname.lastname@example.org...
02 Nov 1998 - Added OnSetFocus(), OnKillFocus() and modified OnPaint() so the control remains beveled
until it actually looses focus - (Vachik Hovhannissian).
code is not in the example listed here.
I tried to implement it myself and it works fine for DROPDOWNLIST style combo boxes, but not for DROPDOWN
style combo's which have a child EDIT control. The latter style does not receive the proper
setfocus/killfocus messages, the child edit control gets them to the focus cannot be accurate.
Has anybody experienced this and found a solution before?
When testing your code to see if color changes where handled properly I noticed some painting glitches. If
you go to the Control Panel->Display Appearence tab and change the scheme from "Windows
Standard" to someting else like "Pumpkin(large)" the thumb doesn't paint right. Upon further
testing I noticed that the thumbs in the combo box on the Display property sheet didn't resize either. The
bug seems to be in MS's code. So instead of using GetSystemMeterics() on every paint you have to call it once
during initialization and store the value. ( like in a member variable). Also instead of calling
GetSystemColor() over and over it would be better to store the colors in member vars and handle the
OnSystemColorChange message to reset them if neccesary IMHO.
The following is a list of inconsistencies the flat combo has compared with MSWord:
1. The height of the control is not the same as MSWord even when the same font is used "Tahoma".
2. When changing the default size of a scroll button via control panel the Flat Combo button when created
has the same size (as is the case with normal Combos), however MSWord does not change based on this setting.
I think it is better to follow the MSWord approach especially on toolbars.
3. (Related to point 2) Drop button is not the same size as MSWord.
4. When the control is disabled the drop arrow does bit have the same colour as MSWord flat combo.
5. When the flat control gets focus it does not stay in 3D mode.