🚀 go-pugleaf

UO wrote:


>After creating the window, because the code in "case WM_TIMER:" takes more 
>time than the poll time of the timer,

Then you need to increase the timer amount.

> do WM_TIMER messages fill the message queue buffer in the end?

I think so.
Another thing to try is to show the elapsed time between WM_TIMER.
Vary the code so it stalls for a while,
then bypasses to zip through any backlog.
Take note of the time, especially if it is less than the Timer amount.

> I've noticed, the line marked with "A" never executes, that means g_cnt is never greater 
>than one.

They run sequentially, so the counter never varies.

>    case WM_TIMER:
>        g_cnt++;
>            sprintf(buf, "g_cnt=%d", g_cnt);
>            MessageBox(hwnd, buf, "info", MB_OK); //B
>        g_cnt--;
>    break;
>
>What is the difference between Code //1 and Code //2 ?

Well, Code 2 calls MessageBox every time while Code 1 never does.
Seems obvious that MessageBox is processing messages.
As a further test, add another counter and display it on your Form.

        g_cnt++;
        g_cnt2++;
            sprintf(buf, "g_cnt=%d  g_cnt2=%d", g_cnt, g_cnt2);
		Form1->Label1.SetTextBuf( buf );
        g_cnt--;

Win32API alternative to VCL SetTextBuffer is
	SendDlgItemMessage( hwnd, nIDDlgItem, WM_SETTEXT, 0, (LPARAM)buf );
 
You should see cnt2 increase while cnt1 remains 1.

>I've never noticed that "case WM_TIMER:" and "case WM_PAINT:" are executed
>simultanously. Is it always true in this case?

Yes.
Messages all happen sequentially in the main thread.
This isn't an interrupt system.
The thread that owns the window executes each message in the queue.

What you were seeing with MessageBox was the main thread
processing WM_TIMER, then running/processing MessageBox,
processing WM_TIMER within that window, then recursing on
down until the stack or resources run out.

The way you get around that is to guard the code:
>    case WM_TIMER:
	if( 0 == g_cnt )
	{
	    ++g_cnt;
            sprintf(buf, "g_cnt=%d", g_cnt);
            MessageBox(hwnd, buf, "info", MB_OK); //B
	    --g_cnt;
	};
>    break;


Multithreaded apps however, can be working on different
messages, just not for the same form instance.