You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When using SetTimer(NULL,NULL,,NULL) the WM_TIMER events are not being sent to the Window. I can see OTVDM passing the API Correctly onto the win32 API SetTimer, but using Spy++ to monitor windows messages cannot see any WM_TIMER messages with wParam matching the ID returned by SetTimer being sent to the Window.
If HWND is specified the timer message is received in WndProc handler (As expected)
Expected behavior
This example code should work., as it does in Windows XP and Windows 10 with NTVDM and the line MessageBox(hwnd,"Hit Timer","Timer!!",MB_OK); should be hit.
UINT myTimer = SetTimer(NULL,NULL,10000,NULL);
printf("Timer created with ID = 0x%08X\n",myTimer);
BOOL fRetVal = TRUE;
for(;;)
{
while (PeekMessage(&msg, NULL, 0, 0, PM_REMOVE))
{
if (msg.message == WM_TIMER && msg.wParam == myTimer )
{
MessageBox(hwnd,"Hit Timer","Timer!!",MB_OK);
}
if (msg.message == WM_QUIT)
return TRUE;
TranslateMessage(&msg);
DispatchMessage(&msg);
}
Screenshots
Under OTVDM on Windows 10 x86
On the same machine but using NTVDM:
Environment (please complete the following information):
Tested on Windows 11 (21H2 build 22000.739) x64 and Windows 10 (10.0.19044.1889) x86
[MsgTst.zip](https://github.com/otya128/winevdm/files/9465884/MsgTst.zip)
Traces and test program
[trace.zip](https://github.com/otya128/winevdm/files/9465879/trace.zip)
The text was updated successfully, but these errors were encountered:
If HWND is specified the timer message is received in WndProc handler (As expected)
Expected behavior
This example code should work., as it does in Windows XP and Windows 10 with NTVDM and the line MessageBox(hwnd,"Hit Timer","Timer!!",MB_OK); should be hit.
Screenshots
Under OTVDM on Windows 10 x86
On the same machine but using NTVDM:
Environment (please complete the following information):
The text was updated successfully, but these errors were encountered: