Changing the Color of Edit and Combobox Controls in ATL

Simply follow these steps in order to change the color of the Edit control or Combobox control in ATL.
  1. Add a handler for WM_CTLCOLOREDIT
    MESSAGE_HANDLER(WM_CTLCOLOREDIT, OnCtlColorEdit)
    
  2. Implementation of the handler, return the brush that u want to use to color the control
    LRESULT OnCtlColorEdit(UINT uMsg, 
                           WPARAM wParam, 
                           LPARAM lParam,
                           BOOL& bHandled)
    {
     HDC hdcEdit = (HDC) wParam;    // handle to display context 
     HWND hwndEdit = (HWND) lParam; // handle to static control 
    
     if (( hwndEdit == GetDlgItem(IDC_EDIT) 
     || ( hwndEdit == GetDlgItem(IDC_COMBO))
     {
      // m_hBrush is an instance variable that stores the
      // current Color brush. If this is the first time through
      // we need to create it. The brush is deleted in the destructor
      if ( m_hBrush == NULL )
       m_hBrush = CreateSolidBrush( RGB(255,0,0)
     )
     
      // Get the DC provided and set the appropriate attributes
     
      SetBkMode(hdcEdit, TRANSPARENT );
      SetBkColor(hdcEdit, RGB(255,0,0));
    
      // Return a handle to the brush
      HBRUSH far* hbr = (HBRUSH far*) m_hBrush;
      return ((DWORD) hbr);
     }
     return 0;
    }
    


Comments

  • There are no comments yet. Be the first to comment!

Leave a Comment
  • Your email address will not be published. All fields are required.

Top White Papers and Webcasts

  • Instead of only managing projects organizations do need to manage value! "Doing the right things" and "doing things right" are the essential ingredients for successful software and systems delivery. Unfortunately, with distributed delivery spanning multiple disciplines, geographies and time zones, many organizations struggle with teams working in silos, broken lines of communication, lack of collaboration, inadequate traceability, and poor project visibility. This often results in organizations "doing the …

  • With JRebel, developers get to see their code changes immediately, fine-tune their code with incremental changes, debug, explore and deploy their code with ease (both locally and remotely), and ultimately spend more time coding instead of waiting for the dreaded application redeploy to finish. Every time a developer tests a code change it takes minutes to build and deploy the application. JRebel keeps the app server running at all times, so testing is instantaneous and interactive.

Most Popular Programming Stories

More for Developers

Latest Developer Headlines

RSS Feeds