Resource size problem...

I know there are two ways to create a control:

1. using resource:

Code:

---

EDITTEXT        IDD_CONTROL, 10, 50, 80, 14, ES_AUTOHSCROLL

---

2. creating the window yourself:

Code:

---

CreateWindowEx(NULL, "Edit", "", WS_CHILD | WS_VISIBLE,
10, 50, 80, 14, hDlg, (HMENU)IDD_CONTROL,
GetModuleHandle(NULL), NULL);

---

As you may noticed, the location and size is the same: 10, 50, 80, 14.
The problem is the way the CreateWindowEx() fucntion sees the value, which is different than the way the resource sees it.

Is there any way I could match them?



Thank you.

Resources dimensions are calculated in dialogbox units, non-resource windows use pixels. Dialogbox units are relative to the font size (usually the system font - see GetDialogBaseUnits). MapDialogRect can convert from dialogbox units to pixels.

But this is a control, not text that uses a font.
Can you please give me an example?

>>But this is a control, not text that uses a font.<<

It doesn't matter: dialogbox units are based on font dimensions.

>>Can you please give me an example?<<

There's one here with a little discussion.

this single line crashes the program:

Code:

---

RECT ref;

MapDialogRect(hDlg, &ref);

---

So I checked the msdn again... take a look at the hDlg part:

Quote:

---

BOOL MapDialogRect(
HWND hDlg, // handle of dialog box
LPRECT lpRect // address of structure with rectangle
);

Parameters
hDlg
Identifies a dialog box. This function accepts only handles for dialog boxes created by one of the dialog box creation functions; handles for other windows are not valid.
lpRect
Pointer to a RECT structure that contains the dialog box coordinates to be converted.

---

>>this single line crashes the program<<

I cannot induce a crash with mingw or msvc.net2003 with winxp although MapDialogRect does return zero with non-dialog windows.

If you are not changing the font of your controls' then GetDialogBaseUnits will return dialogbox units based on the system font which you can use to convert to pixels. An example of its use ('using combo boxes') can be found on the msdn page for the function, a link to which I have provided in a previous post.

well, maybe because i'm on win98... but still, could it be because I'm not creating the dialog with a function, instead I create it with a resource.

When the MapDialogRect function mentions dialog boxes created by one of the dialog box creation functions it is referring to:

CreateDialog
CreateDialogIndirect
CreateDialogIndirectParam
CreateDialogParam
DialogBox
DialogBoxIndirect
DialogBoxIndirectParam
DialogBoxParam

All of these functions rely on a dialog template generated either in memory or from a resource script.

thank you

just one last thing.

I've noticed that the convertion is not 100% accurate... actually it more like 85%.

Is there a way I could make it a 100%?