AutoHotkey Community

Here are the changes for v1.0.41:

Fixed "Transform HTML", which was broken by v1.0.40.02. [thanks Rabiator]

Improved syntax to support One True Brace (OTB) style with IFs, ELSEs, functions, and normal loops.

Added built-in variable A_AhkPath, which contains the full path and name of AutoHotkey.exe (if available).

Added directives #IfWinActive/Exist to enable selected hotkeys and hotstrings for only the windows you specify.

Thanks for the OTB, although it will require to change a lot in the Auto-Syntax-Tidy, I believe it is a good improvement.

_________________
Ciao
toralf

Yeah!
I don't care much for the OTB, as I don't use this style of coding, but it is nice for those which cannot live without it...

I eagerly awaited the context sensitive hotkeys.
Indeed, there was workarounds like:but it wasn't very nice, adding a lot of code and not being very readable.
Your solution is nice, very well made (the idea of group of windows is excellent) and practical.

Congratulations, you are doing an excellent job on this software!

The OTB feature adds greater flexibility to the way scripters can code which is terrific. The window-specific hotkeys are also a useful addon. Thanks Chris.

Thanks. The #IfWin feature isn't as useful as I'd originally envisioned because I ran into some roadblocks when trying to implement it (such as thread-safety in the hook thread).

Hopefully the feature will get improved to support %Var% in parameters. Eventually, it may also allow duplicate hotkey labels as Evl suggested at http://www.autohotkey.com/forum/viewtopic.php?t=7485

I would like to see that. Thanks for this very usefull release.

Kinda coincidence . I had a look at Perl two days ago. To get into the right mood for that, I've checked a script of one of my colleagues and have seen that style of coding for the first time (well, I'm not a programmer ). Whopeee, that means that I can use the same technique with AHK & Perl.

Thx.

With the #IfWin directives, can ahk_id be added as a WinTitle option? The use will be rare, so only if it doesn't add a lot of code size or time to add.

thanks,
beardboy

As beardboy said, it would be handy - it would also be more consistent with other commands. To be useful though, it would need to be able to accept variables for the ID (as Chris already mentioned might be added).

I believe ahk_id and ahk_pid are already supported. The only reason they're not mentioned is what Evl said: Without %Var% support, they would be useful only in unusual circumstances such as a script creating another script via FileAppend.

However, it might be of use that GroupAdd can add a series of ahk_id's or ahk_pid's to a group. You can then use that group with #IfWin. Also, you can keep adding more id's and pid's to such a group as long as you want -- and as long as the list doesn't get huge, performance shouldn't be affected much.

Chris, thanks for the work around solution.

thanks,
beardboy

Here are the changes for v1.0.41.01:

Fixed AltGr hotkeys that send AltGr characters such as "<^>!a::Send \" in German. [thanks AGU]
Fixed Gui +Disable/AlwaysOnTop to work even if other options are present on the same line. [thanks evl]
Improved syntax to support having a command on the same line as an open-brace. [thanks segfault]

The tentative plan for the next major release is to support duplicate hotkeys and hotstrings for easier context sensitivity with the #IfWin directives.

Nice one however this does not apply to OTB. Is this intentional?

For example this works:But not this (OTB):

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

Yes, it's intentional because the extra code size didn't seem justified given how rarely anyone would want to use such an ugly style

It is also documented on the Block page under the OTB section: "However, open-braces of the One True Brace style do not support commands to their right."

Well, I do find the first style (the one you just allowed) ugly too, perhaps that's why it is rarely used.
Ugly and impratical if you have to add a new command just before the first line of the block.
And with no clear advantage over the OTB style, ie. no gain of line. Well, at least, braces are aligned, I find this more readable than OTB.

But well, it is good to have flexibility and to please as much people as possible, as long this doesn't bloat the code. Which seems to be a true concern for Chris I like that.