AutoHotkey Community

Dear corrupt,

Very comprehensive list and nicely done!

just a doubt:

WS_OVERLAPPEDWINDOW := (WS_OVERLAPPED Or WS_CAPTION Or WS_SYSMENU Or WS_THICKFRAME Or WS_MINIMIZEBOX Or WS_MAXIMIZEBOX)

What does that Or do ? Sorry for the noobish question!

My CSV version has only integers for the second field, like:

WS_OVERLAPPEDWINDOW := 0xCF0000

Is it worth evaluating and converting all these into numbers?

Regards,

Thanks . There may be a few bugs though. I used a script to process the list and have only inspected a few random vales so far.

I think it should probably read WS_OVERLAPPED | WS_CAPTION | WS_SYSMENU | WS_THICKFRAME | WS_MINIMIZEBOX | WS_MAXIMIZEBOX

It might be. It probably depends on how you use the constants in your code. If you use them as variables then it shouldn't be necessary but if you add the output in a comment then use the value in the code then it would be convenient. I'm currently using adding comments and adding values to the code but might switch to using variables soon for readability.

Would not something like this be better ?



Thanks for suggesting API viewer 2004. I had never used it.

Search Keywords: api constants value hex

_________________

ʞɔпɟ əɥʇ ʇɐɥʍ

I chose the title to be Win32 constants because some of the constants can be used directly in AHK.

Need to remember this post as im always lookign for it

This is absolutely beautiful. I have been struggling with figuring these out. No more! Thanks for the handy tool.

_________________
Ben

My Trac projects
My Wiki
[Broken] - My music

Trying to track down a Win32 constant can many times be very frustrating. After remembering that I had downloaded this tool a while back I was able to find several constants that were difficult if not impossible to find otherwise.

Thanks. Keep up the good work!

...unfortunately a straight Google on the constant most/some of the time doesn't get the number, it normally gets the MSDN article about the constant, but not the number behind it...however using my VARNAME site:ddart.net...trick (mentioned here), normally DOES work...click the link, then replace VARNAME with a windows constant, like WM_COMMAND...

Also can I take this time to encourage everyone to assign the constant, not just lookup the number then put the number directly in the code...

For example...don't do this...


...but instead do this...


...& no, I don't like seeing this either...


...a comment explaining it doesn't help me...best to define all the constants in one place, so the rest of the code is clear. The whole reason Windows has these constants is so people DON'T have weird numbers all over the code, but it seems as if most AutoHotkeyers like magic numbers littering their code...

AutoHotkey doesn't have #define so what's the point of creating useless variables. If you have a performance critical application it makes more sense to hard code the value than to XAND if you know every value.

That's not the only reason.

Hey Skan I've just compiled a list of Vista 32bit ANSI constants if you're interested

_________________
GitHub • Scripts • IronAHK • Contact by email not private message.

It depends... In compiled, optimized code constants don’t cost anything, but sometimes make the code more readable. Not always. But in an interpreted language constant names are added to the table of variables, consuming memory and slowing down all dynamic variable references: the interpreter has to search for the name in a longer list. In AHK I prefer

...well of course I want a #define & I also want to hide all the "useless variables"...but I work with what I've got...I've only got "normal" vars, so I use em...


...ah!...didn't think of a performance hit, I only noticed the "useless variables" in ListVars...but until AutoHotkey gets #define, I'll just have to live with the performance hit, since I can't stand magic numbers in code...

For completeness, I'd like to mention AutoHotkey needs #define, working exactly like C's define...replace all #defines at load-time, so there's not run-time performance hit...which also hides #defines from ListVars...& also perhaps a Const option...with does almost the same as a #define, cept would be listed in ListVars...so a Const would only be resolved once at load-time but be visible in ListVars (for whatever reason)...

. thanks Titan, I will look into it.

If you don't mind me reviving this topic, I'd have a suggestion:
since (sadly) Vista is taking up more and more users percentage but there still are Win9x users (like myself, for example), I thought it would be a good idea to add another field to the window, to show the Windows version range the selected constant can be found in.

This would be helpful in avoiding the usage of unsupported constants in older Windows versions.

Also, a small note: on my Win98SE system I couldn't find any icon in USER32.DLL, so I just switched to USER.EXE, which shows the info (i) icon.
The code could be modified as follows:
if A_OSVersion in WIN_95,WIN_98,WIN_ME
Menu, Tray, Icon, C:\Windows\System\USER.EXE, 5
else
Menu, Tray, Icon, USER32.DLL, 5

_________________
AHK tools by Drugwash (AHK 1.0.48.05 and Win98SE)