Sometimes when scripting and I need to make an Interop.Call call to a Windows API function that takes a parameter which is a constant, such as MB_OK for MessageBox or WM_CLOSE for SendMessage, I need to find out the value of the constant and the way I do this is open Visual Studio, type the constant name and hover over it so that the tooltip tells me the value. That method sucked. I googled for a reference of all the constant values and I didn't find much either.

I then remembered VB came with a file called WIN32API.TXT that contained all the Constants, Declares and Types used by the Win32 API functions. However I didn't like the format of the file (as I don't like VB's syntax anyway) so I used a combination of (regex) find/replace and various other things to format the file the way JScript developers would find most convenient. I removed the useless Declares and Types, changes &H for hex into 0x, And and Or into & and |, and made each line follow the format 'var CONST = 0xVALUE;' so that it's possible to easily copy and paste it into your script should you want to.

The file is hosted here: [EDITED: file found to be inaccurate/incomplete]

Here's a version wrapped in the Windows object to keep your script tidy

http://zivontsis.googlepages.com/win32api.txt

quote:

---

Originally posted by ShawnZ
Here's a version wrapped in the Windows object to keep your script tidy

http://zivontsis.googlepages.com/win32api.txt

---

Yes segosa, the point was to have it in an external script file.

http://www.pinvoke.net/ has user32 functions and a whole load of other stuff.  deAd found that one.

quote:

---

Originally posted by alexp2_ad
http://www.pinvoke.net/ has user32 functions and a whole load of other stuff.  deAd found that one.

---

Thats because the website is for C# and VB's Pinvoke functionality

quote:

---

Originally posted by ShawnZ
Yes segosa, the point was to have it in an external script file.

---

quote:

---

Originally posted by segosa
I then remembered VB came with a file called WIN32API.TXT that contained all the Constants, Declares and Types used by the Win32 API functions.

---

It'd be helpful if you pointed out where exactly it didn't work...

quote:

---

Originally posted by CookieRevised
I strongly suggest to get a list from somewhere else. WIN32API.TXT is known to contain a lot of mistakes, wrong values and not to mention far from being complete.... unfortunatly.

---

quote:

---

Setting aside that WIN32API.TXT isn't a reliable source for this, both files (the one from Segosa and the one from Shawnz) contain leftover texts too (because of the way they were automatically created without checking the output?).

---

code:

---

Windows.prototype.SECTION_ALL_ACCESS = STANDARD_RIGHTS_REQUIRED | SECTION_QUERY | SECTION_MAP_WRITE | SECTION_MAP_READ | SECTION_MAP_EXECUTE | SECTION_EXTEND_SIZE;

---

quote:

---

Originally posted by segosa
Have you got any examples of wrong constant values? Why is WIN32API inaccurate? I'm sure Microsoft don't change the values of constants whenever they're bored...

---

quote:

---

If you spend just a few seconds browsing WIN32API (or it's database twin), you'll see the hundreds of functions that are yours for the calling. So why wouldn't you use it? Well ... because it may be impressive, but it's often just not correct. Here's what Bruce McKinney says about it, "Unfortunately, WIN32API.TXT has a well-earned reputation for being full of errors." Dan Appleman agrees, "Frankly, Win32API.TXT is not perfectly good. In fact, it's not even close."
(..)

---

quote:

---

Originally posted by segosa

quote:

---

Originally posted by CookieRevised
Setting aside that WIN32API.TXT isn't a reliable source for this, both files (the one from Segosa and the one from Shawnz) contain leftover texts too (because of the way they were automatically created without checking the output?).

---

Please point out an example...

EDIT: shawnz, I think the reason yours doesn't work is because of stuff like this:

code:

---

Windows.prototype.SECTION_ALL_ACCESS = STANDARD_RIGHTS_REQUIRED | SECTION_QUERY | SECTION_MAP_WRITE | SECTION_MAP_READ | SECTION_MAP_EXECUTE | SECTION_EXTEND_SIZE;

---

STANDARD_RIGHTS_REQUIRED and so on should be Windows.STANDARD_RIGHTS_REQUIRED for example, I think..

---

quote:

---

Originally posted by CookieRevised
indeed, but not only that, both files also contains leftover text. Simply scroll your created files quickly and you'll notice it in an instant.

---

quote:

---

Originally posted by segosa
Hmm, I see now, just a place where my regex didn't catch a Type declaration. I'd bother fixing it, but I suppose the file's a bit useless now since it's inaccurate/incomplete

---

http://m00.cx/win32api.txt

Does it get the CookieRevised seal of approval?

EDIT: Bah, VB also has Not which needs to be converted too.

* segosa fixes..

Nope, there are sill many many errors. Some could be in the original file also, but most are caused by the auto-converting.


Stuff like:
var ADDRESS = ADDRESS64;
=> ADDRESS64 isn't defined as it was a structure

var ADDRESS_SIZE = sizeof(ADDRESS);
var ADDRESSINFO_SIZE = sizeof(ADDRESSINFO);
=> sizeof() is invalid in JScript and also these were structures

var AGENTAUDIOERROR_DEVICE = AGENTAUDIOERROR(1);
=> Arrays which aren't defined

var ALID_CHARSET = VALID_CHARSET = -27;
=> Dunno if this is due to the auto-converting or if this was already so in the original file. But it doesn't make much sense. Might need to check with the msdn library.

var AMF_AUTOMATICGAIN = -1#;
=> # isn't valid in JScript

var BEGIN_INTERFACE = virtual void a() {};
=> hmmmm....

var BFT_LOG = "\x01" | BFT_LOG_DIRECTORY;
=> Makes even less sense (boolean comparisson between a string and a number)

var CANNOT_LOAD = UINT(-8);
=> Dunno if this was in original file or not.

var ALG_CLASS_DATA_ENCRYPT = (3 * 2 ^ 13)
=> In JScript ^ means bitwise XOR, not the same as taken the power of which is meant here.


Also check every negative number. As I said earlier, a negative 'integer' isn't the same as the same number as a negative 'long'. eg: -1 as an integer (2bytes) is 65535 as a long (4bytes).


All these examples or only one example of the same kinds I got from quicky browsing the file, the file is full of things like these...

quote:

---

Originally posted by CookieRevised
Nope, there are sill many many errors. Some could be in the original file also, but most are caused by the auto-converting.


Stuff like:
var ADDRESS = ADDRESS64;
=> ADDRESS64 isn't defined as it was a structure

var ADDRESS_SIZE = sizeof(ADDRESS);
var ADDRESSINFO_SIZE = sizeof(ADDRESSINFO);
=> sizeof() is invalid in JScript and also these were structures

var AGENTAUDIOERROR_DEVICE = AGENTAUDIOERROR(1);
=> Arrays which aren't defined

var ALID_CHARSET = VALID_CHARSET = -27;
=> Dunno if this is due to the auto-converting or if this was already so in the original file. But it doesn't make much sense. Might need to check with the msdn library.

var AMF_AUTOMATICGAIN = -1#;
=> # isn't valid in JScript

var BEGIN_INTERFACE = virtual void a() {};
=> hmmmm....

var BFT_LOG = "\x01" | BFT_LOG_DIRECTORY;
=> Makes even less sense (boolean comparisson between a string and a number)

var CANNOT_LOAD = UINT(-8);
=> Dunno if this was in original file or not.


Also check every negative number. As I said earlier, a negative 'integer' isn't the same as the same number as a negative 'long'. eg: -1 as an integer (2bytes) is 65535 as a long (4bytes).


All these examples or only one example of the same kinds I got from quicky browsing the file, the file is full of things like these...

---