Do not receive focus events in console

Hi There,

I thought this must have been asked many times. I use something like:

Code:

---

    static HANDLE stdinHandle = GetStdHandle(STD_INPUT_HANDLE);

    const DWORD consoleInputCommandMode = ENABLE_ECHO_INPUT + ENABLE_PROCESSED_INPUT;
    SetConsoleMode(stdinHandle, consoleInputCommandMode);
    FlushConsoleInputBuffer(stdinHandle);

    INPUT_RECORD record;
    DWORD numRead;

    switch (WaitForSingleObject(stdinHandle, 1000)) {
        case(WAIT_OBJECT_0):
        if (ReadConsoleInput(stdinHandle, &record, 1, &numRead)) {
            if (record.EventType != KEY_EVENT) {
// THIS IS THE PROBLEM, I just want key events, nothing else
            }
        }
            break;
    }

---

I could disable mouse events but MENU_EVENT 0x0008 and FOCUS_EVENT 0x0010 keep coming.

How can I get rid of those - I cannot see an option in SetConsoleMode;

Thank you :)

Well this is based upon how I do this. I use client/server with a shared circular buffer. This code is part of the console server and obtains chars from the keyboard and puts them in the buffer and converts 'special' codes depending upon conCodes array. The client code just takes chars from the buffer when any are available. I do it this way so that there can be different servers (eg I also have one for telnet).

nterm->getstdin() returns a handle to the console input (stdinHandle).

Code:

---

....
for (char ch; WaitForSingleObject(nterm->getstdin(), INFINITE) != WAIT_TIMEOUT; ) {
                bool got {};

                if (DWORD no {}, evt {}; GetNumberOfConsoleInputEvents(nterm->getstdin(), &no) && no)
                        if (const auto ibuf {std::make_unique<INPUT_RECORD[]>(no)}; ReadConsoleInputA(nterm->getstdin(), ibuf.get(), no, &evt) && evt == no)
                                for (DWORD r {}; r < evt; ++r)
                                        if ((ibuf[r].EventType == KEY_EVENT) && ibuf[r].Event.KeyEvent.bKeyDown)
                                                if (const auto ker {ibuf[r].Event.KeyEvent}; ker.wVirtualKeyCode >= 0x21 && ker.wVirtualKeyCode <= 0x2f) {
                                                        nterm->in.wait_enqueue(conCodes[ker.wVirtualKeyCode - 0x21]);
                                                        got = true;
                                                } else
                                                        if (ch = ker.uChar.AsciiChar; ch) {
                                                                nterm->in.wait_enqueue(ch);
                                                                got = true;
                                                        }

                                                if (got)
                                                        nterm->setInpEvt();

                                                ResetEvent(nterm->getstdin());
        }
....

---

Hmm, I was hoping that no threads will be needed - basically I would like to print something on timeout and something else on keypressed.

You might be right and the idea is probably difficult since key pressed events are received multiple times while a key kept pushed, only release is received just once - so holding key is treated as multiple key press events.

No. You don't need threads. I just pasted as an example some of my code which is within a thread and explained why a queue is used. Where it uses wait_enqueue() just directly use the char. Alter the code as needed. It's just an example as a starter.