What else then keyboard input trigger EET_KEY_INPUT_EVENT?

[MasterGod]

When there's a EET_KEY_INPUT_EVENT event, what may cause it except a keyboard hit?

Edit:

Thanks but I meant that is the..
I'll rewrite the question:
Is the engine designed in a way that only input devices such as the keyboard will trigger that event?

[Morgawr]

When there's a EET_KEY_INPUT_EVENT event, what may cause it except a keyboard hit?

Calling a dos interrupt? Not sure...

[CppJunky]

Some code sending fake messages in order to force the event? (dirty stuff, but Its beeing done sometimes)

[rogerborg]

Depends on the device. I can only find 3 places where that event is generated:

CIrrDeviceLinux.cpp
In CIrrDeviceLinux::run()

CIrrDeviceSDL.cpp
In CIrrDeviceSDL::run()

CIrrDeviceWin32.cpp
In WndProc()

(grep for 'EventType = irr::EET_KEY_INPUT_EVENT' to find them)

You could stick a breakpoint on each one and find out.

[MasterGod]

Thanks but I meant that is the..
I'll rewrite the question:
Is the engine designed in a way that only input devices such as the keyboard will trigger that event?

[rogerborg]

I can't see any way other than a device keyup/keydown event.

Windows:
case WM_KEYDOWN:
case WM_KEYUP:


SDL
case SDL_KEYDOWN:
case SDL_KEYUP:

Linux:
case KeyRelease:
case KeyPress:

[JP]

Are you getting keyboard events that you're not expecting or do you want to fire a keyboard event yourself (not sure why you'd want to do that though)?

I think you need to explain yourself a bit better when posting questions

[MasterGod]

I just wanted to be sure that's the way it's working.

[rogerborg]

Then don't take our word for it.