Hi,
I am little confused about the processing of WM_InvalidateRect signal. I did some coding and found that processing of WM_InvalidateRect happen at the end of the function. i.e. for example,
void some_function()
{
....do_something1_
WM_InvalidateRect(hWin,&Rect);
...do_something2..
...do_something3...
}
Here, I am calling WM_InvalidateRect function after do_something1_,
WM_InvalidateRect sends the signal to window to update the specified area right ? but here controller doesn't jumps to WM_PAINT as soon as this Invalidate API is called.. It first processes do_something2 & do_something3 and then it jumps to WM_PAINT event.
so In short current behaviour is :
1) do do_something1_
2) Invalidate the rect
3) do do_something2_
4) do do_something3_
5) Repaint the window
Is it the correct behaviour ??
how can i achieve behaviour like this :
1) do do_something1_
2) Invalidate the rect
3) Repaint the window
4) do do_something2_
5) do do_something3_
I am little confused about the processing of WM_InvalidateRect signal. I did some coding and found that processing of WM_InvalidateRect happen at the end of the function. i.e. for example,
void some_function()
{
....do_something1_
WM_InvalidateRect(hWin,&Rect);
...do_something2..
...do_something3...
}
Here, I am calling WM_InvalidateRect function after do_something1_,
WM_InvalidateRect sends the signal to window to update the specified area right ? but here controller doesn't jumps to WM_PAINT as soon as this Invalidate API is called.. It first processes do_something2 & do_something3 and then it jumps to WM_PAINT event.
so In short current behaviour is :
1) do do_something1_
2) Invalidate the rect
3) do do_something2_
4) do do_something3_
5) Repaint the window
Is it the correct behaviour ??
how can i achieve behaviour like this :
1) do do_something1_
2) Invalidate the rect
3) Repaint the window
4) do do_something2_
5) do do_something3_