Handle of client area?

[sawer]

Unlike menus, tool and status bars are seperate controls that live inside the parent window's client area. Therefor if we just leave our WM_SIZE code from before, they are going to overlap with the edit control we added in the previous examples
http://www.winprog.org/tutorial/app_three.html

If so why GetClientRect Function returns the upper-left and lower-right visible corners of the client area? It must be start under toolbar. right?

Is there a way to get handle of clent window(area), so we can move it?

[Skizmo]

Is there a way to get handle of clent window(area), so we can move it?

Which handle do you mean.. and what do you want to move ?

[sawer]

I mean client area's handle. But now i think this can't be true.

But if toolbar lives inside the parent window's client area, so client orgin must be started above visible area. If not, how can client area be moved?

Also file menu doesn't live in client area, so client area must be moved, right?( I am confused about client area place after adding menu, status bar and toolbar. )

[GCDEF]

I mean client area's handle. But now i think this can't be true.

But if toolbar lives inside the parent window's client area, so client orgin must be started above visible area. If not, how can client area be moved?

Also file menu doesn't live in client area, so client area must be moved, right?( I am confused about client area place after adding menu, status bar and toolbar. )

I'm confused. You don't move a client area or get a handle to a client area. You get a handle to a window and move the window.