R
Romano Scuri
Under Windows 2000 service pack 2 and biprocessor system
if I use
SetTimer(hWnd,IDC_TIMER1,50,NULL); // Post WM_TIMER to main Window
it work. Instead if I use
SetTimer(hWnd,IDC_TIMER1,50,TimerProc); // Call TimerProc callback
when the user interact with the program it work and freeze when the program
run without interaction.
(The Timer update status bar with system date/time and I see that the
seconds stop updating)
On uniprocessor systems all OK.
Is this behaviour already known ? Is it a feature (Not a bug ;-) ?
Thanks for answer...
if I use
SetTimer(hWnd,IDC_TIMER1,50,NULL); // Post WM_TIMER to main Window
it work. Instead if I use
SetTimer(hWnd,IDC_TIMER1,50,TimerProc); // Call TimerProc callback
when the user interact with the program it work and freeze when the program
run without interaction.
(The Timer update status bar with system date/time and I see that the
seconds stop updating)
On uniprocessor systems all OK.
Is this behaviour already known ? Is it a feature (Not a bug ;-) ?
Thanks for answer...