Thread: Highlighting text in an EditBox

I am trying to set my editbox up so that when the user clicks on an edit box, the text inside the editbox will automatically become highlighted. I figured sending an EM_SETSEL message on every EN_SETFOCUS notification would do that easily, except for the little snag that it isn't working: the caret position scrolls to the right a bit, but thats about it... no text is highlighted at all. Here is my simple code:

Code:

case EN_SETFOCUS:
{
     SendMessage((HWND)lParam, EM_SETSEL, (WPARAM)0, (LPARAM)-1);
     break;
}

According to MSDN, a wparam of 0 and an lparam of -1 should select all text, but it does not do this (nor for any combination of start/end values I have tried).
There's probably some simple thing I'm missing, but other than that I have no clue as to why something so simple has become so hard, please help, thanks.

Yes, that was just a small snippet cut out from the larger WM_COMMAND message catch.
Here is the more complete form:

Code:

  case WM_COMMAND:
       switch(LOWORD(wParam))
       {
           case IDC_NAMEEDIT:
               switch(HIWORD(wParam))
               {
                   case EN_SETFOCUS:
                       SendMessage((HWND)lParam, EM_SETSEL, (WPARAM)0, (LPARAM)-1);
                       break;
                   default:
                       return FALSE;
               }
               break;
     ....

I know for sure it's firing because I tested it by putting a messageBox in the notification, which pops up as expected every time I focus the edit box. As I mentioned, it makes some signs of an attempt to highlight (the caret scrolls right) but no actual text is highlighted, what is going wrong here?

This is my guess to what is happening.

According to the docs:

ES_NOHIDESEL
Negates the default behavior for an edit control. The default behavior hides the selection when the control loses the input focus and inverts the selection when the control receives the input focus. If you specify ES_NOHIDESEL, the selected text is inverted, even if the control does not have the focus.

So I speculate this is what happens when you send the EM_SETSEL:
1. The edit control gains focus.
2. EN_SETFOCUS is called.
3. You send the EM_SETSEL message which is processed.
4. The control restores the selection from before it lost focus, thus reversing your EM_SETSEL.

When you post a message, it is added to the message queue rather than being called immediately, so the sequence of events is now:
1. The edit control gains focus.
2. EN_SETFOCUS is called.
3. You post the EM_SETSEL message which waits in the message queue.
4. The control restores the selection from before it lost focus.
5. The EM_SETSEL message in the queue is processed.

Incidentally, I thought of this when I first read your post but couldn't think of a neat solution, so nice work Ken for suggesting PostMessage.