Hi,
How do you know that:
MB_OK is 0h in hex value or
VK_ESCAPE is 1Bh
is there a reference out there that points me on how to determine that this one is 1h or 0040h...
I hope i explained it clearly !!! gulp!
Thanks
How do you know that:
MB_OK is 0h in hex value or
VK_ESCAPE is 1Bh
is there a reference out there that points me on how to determine that this one is 1h or 0040h...
I hope i explained it clearly !!! gulp!
Thanks
Hi umberg6007
The file windows.inc (found in c:\masm32\include) contains most of the constants used in windows.
KetilO
The file windows.inc (found in c:\masm32\include) contains most of the constants used in windows.
KetilO
I know but how do "they" know that its 0h for MB_OK.
MB_OK could be 1h or 2h or 3h...How did they know the exact hex value.
Thanks
MB_OK could be 1h or 2h or 3h...How did they know the exact hex value.
Thanks
I know but how do "they" know that its 0h for MB_OK.
MB_OK could be 1h or 2h or 3h...How did they know the exact hex value.
Thanks
look into windows.inc:
MB_OK equ 0h
EDIT:
Think you mean M$ with "they".... they made the rules :)
Cause, I was looking into the platform sdk and I found out that
MB_CANCELTRYCONTINUE is one of the MessageBox styles and I look into the WINDOWS.inc and did not find the style.
I'm looking for a reference or steps, if such exists, to translate this into a hex value.
MB_CANCELTRYCONTINUE is one of the MessageBox styles and I look into the WINDOWS.inc and did not find the style.
I'm looking for a reference or steps, if such exists, to translate this into a hex value.
You would have to search the C header files in the PSDK.
...and you find in winuser.h:
...and you find in winuser.h:
#if(WINVER >= 0x0500)
#define MB_CANCELTRYCONTINUE 0x00000006L
#endif /* WINVER >= 0x0500 */Thanks, I never knew that....
:)
:)
Remember, WINDOWS.INC is a "work in progress". It dosn't contain EVERY structure and equate used in Windows, but it does have the most common.
This is especially true for things that were introduced with newer versions of the OS, like XP and ME. If you plan on using this stuff, you may need to dig it out of the .H files, for now at least. :)
This is especially true for things that were introduced with newer versions of the OS, like XP and ME. If you plan on using this stuff, you may need to dig it out of the .H files, for now at least. :)
The C header files are the definitive source for constant values.
When a C++ user #includes windows.h, several .h files get compiled.
In addition to the headers that come with a C++ compiler, there are also sets of DDK headers which include constants and functions that aren't defined in the compiler-supplied headers.
When a C++ user #includes windows.h, several .h files get compiled.
In addition to the headers that come with a C++ compiler, there are also sets of DDK headers which include constants and functions that aren't defined in the compiler-supplied headers.