quote:
Originally posted by ShawnZ
Yes segosa, the point was to have it in an external script file. 
And use an relative extreme amount of otherwise useless memory.....
It might be very usefull for the "quick test driving" and developing of scripts (so you don't waste time on looking up and defining the constants), but I suggest not to use it in released versions and actually define only the ones you need in the released script.
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.
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.
----------
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?). And setting aside that leftover block of text near the end, Shawnz' file will even create more problems as there are a lot of constant names being used as values without linking them to the Windows object.
/ 
