how its done(hyperterminal)?

Originally Posted by CommonTater

Code:

    // dispatch window messages

    while (GetMessage(&msg,NULL,0,0) > 0)
      if (!TranslateAccellerator(GetForegroundWindow(),hAccellerator,&msg)
        if(!IsDialogMessage(GetForegroundWindow(),&msg))
          { TranslateMessage(&msg);
             DispatchMessage(&msg); }

Hmm, I wonder what'll happen if your window isn't the foreground one. Hint, it won't work. Just use the value returned from CreateWindow. You can't fail to receive it, so why eschew it in favour of something incorrect?

Originally Posted by stefan63

Here i found problem with "Enter" key detection - solution i did : trigger on EN_MAXTEXT notification.

To get ENTER keys from an edit control the edit must ahve both the ES_MULTILINE and ES_WANTRETURN styles.

Originally Posted by adeyblue

Hmm, I wonder what'll happen if your window isn't the foreground one. Hint, it won't work. Just use the value returned from CreateWindow. You can't fail to receive it, so why eschew it in favour of something incorrect?

It's done that way so that I can use a single dispatcher for all windows in an application...
Accelerator and Dialog messages should always be directed to the foreground window for tabbing and hotkey activities. If I use MainWind (or similar) in there the dialog actions (tab, space, etc.) only work for one window, not all of them.