My question has several components.
As I understand it, GetClientRect() will fill out a rect structure with the client coordinates for a given window. These returned values are in SCREEN COORDINATES? The origin is (0,0) because the area being returned is the total "client" area within the selected window with the upper left corner being (0,0)?
SCREEN COORDINATES are determined by (I suppose) monitor and adapter capabilities?
CLIENT COORDINATES are SCREEN COORDINATES?
SCREEN COORDINATES are pixels?
CLIENT COORDINATES are pixels?
DEVICE COORDINATES can be pixels?
DEVICE COORDINATES can be referred to as SCREEN COORDINATES?
DEVICE COORDINATES can be referred to as CLIENT COORDINATES?
ClientToScreen() simply updates your rect stucture making your client area relative to the entire screen area (1024X768 as a common example)? This is your window position for the most part (acknowledging the fact the the client area doesn't include certain aspects of the entire window).
So now I know my client area dimensions and its location on the screen?
What does the application of the MapDialogRect function have on the following example:
I do not fully understand the end results of this conversion.
Also, I mentioned earlier what I thought was the "client area" of a window. As I read through some literature I got some mixed signals on "client area". Basically, if you use an API call (as opposed to an MFC call) "client area" may be treated differently.
PS: Very little clear docs on this subject.