Hi,
that happens when you open any new window (file explorer, printf, error, etc) with a pressed key. The engine does not reset its pilot variable (key_... and key_any aswell), so they remain true although the new window is closed. I guess that happens because the key releasing windows event is received by the new window instead of its parent so engines key_... variables manager is never executed for that event. I thought that calling the engines windows callback function with the proper parameters might work but no luck.

Code:
// global prototype
UINT CALLBACK myMsgHandler (HWND hdlg, UINT uiMsg, WPARAM wParam, LPARAM lParam);
// save engines callback function
myMsgHandler = on_message;
// call it on_f5 event
myMsgHandler (hWnd, WM_KEYUP, VK_F5, 0);



Salud!

edited________
ups, late...

Last edited by txesmi; 04/29/18 09:44.