Trap EN_SETFOCUS message and change edit box

[David L Morris]

I thought this would change the edit box display but I must have to do something else to achieve it.  Could someone please guide me?

Under the dlgproc case WM_COMMAND message processing:-

   case WM_CTLCOLOREDIT:
      if ((HIWORD(wParam)) == EN_SETFOCUS)
                {   hdc = (HDC)wParam;
                   SetTextColor(hdc, RGB(255,255,255));   
                   SetBkColor(hdc, RGB(0,0,0));         
                   return (LONG) GetStockObject (WHITE_BRUSH);
            }
      else
                {   hdc = (HDC)wParam;
                   SetTextColor(hdc, RGB(255,0,0));            // red
                   SetBkColor(hdc, RGB(255,255,0));            // yellow
                   return (LONG) GetStockObject (WHITE_BRUSH);
            }
      break;

[DMac]

You have to trap focus and store the handle of the edit box with focus.
You can then switch off of this handle when handling WM_CTLCOLOREDIT.

attached is a demo of this technique.

[David L Morris]

Thanks very much DMac.  I will use your sample to study and include the example in my code.

[David L Morris]

Hello again.  Could you advise how you generated the code in your example please?  I am converting from Basic and got my original code working by using the GetFocus function as follows:-

   case WM_CTLCOLOREDIT:
      if (lParam == (long)GetFocus())
                {   hdc = (HDC)wParam;
                   SetTextColor(hdc, RGB(255,255,255));   
                   SetBkColor(hdc, RGB(0,0,0));         
                   return (LONG) GetStockObject (WHITE_BRUSH);
            }
      else
                {   hdc = (HDC)wParam;
                   SetTextColor(hdc, RGB(255,0,0));            // red
                   SetBkColor(hdc, RGB(255,255,0));            // yellow
                   return (LONG) GetStockObject (WHITE_BRUSH);
            }
      break;

[DMac]

Hello again.  Could you advise how you generated the code in your example please

I assume that you are refering the the message crackers (The lines begining with HANDLE_MSG or HANDLE_DLGMSG) and the associated methods.

I use the message cracker wizard see here: http://forum.pellesc.de/index.php?topic=2352.0

If I am writing a dialog based application I replace the generated HANDLE_MSG macro with the HANDLE_DLGMSG macro.

Our own timovjl has also written a tool: http://forum.pellesc.de/index.php?topic=2065.0

Timo's tool doesn't make use of the message cracker macroes but instead breaks the messages out to the methods in code.

Both of these tools yield clean and managable code.

One more tool that I use quite a bit of is the Cwizard.  The stand alone version is here: http://www.smorgasbordet.com/pellesc/contrib_cwiz.htm and the add-in can be found here: http://forum.pellesc.de/index.php?topic=104.0

I use the stand alone version and have not used the add-in yet.

[David L Morris]

Thanks again and I have downloaded your references to study.  I am going on a few weeks break and will report back on my return.