AutoHotkey Community

v2-Dokumentation an v2.0.17 angepasst.

Mehr Details auf GitHub

Thanks for reporting. I've fixed this.

v2-Dokumentation an v2.0.16 angepasst.

Mehr Details auf GitHub

AutoHotkey uses 1-based icon numbers. There's no icon 0. Add 1 to each icon number and you have the icons you want.

Thanks, but it's not a bug. The exit reason is stored in the hidden first parameter named this. See https://www.autohotkey.com/docs/v2/Objects.htm#Custom_Classes_method

Then show us your script. If it is too large or contains sensitive data, reduce it to a minimum where this supposed bug still occurs.

When I run this script, I get the following output:
As expected, the exit reason is "Exit" and the exit code is 0. The exit code is always 0 unless specified otherwise via Exit or ExitApp.

v2-Dokumentation an v2.0.15 angepasst.

Mehr Details auf GitHub

Commit "Improved reliability of taking focus when a menu popup is shown." has completely fixed the issues (at least for me). WinActivate(A_ScriptHwnd) is no longer necessary. Thanks again, @lexikos

v2-Dokumentation an v2.0.14 angepasst.

Mehr Details auf GitHub

If you are going to use #Requires in a bug report, it would be prudent to correctly specify the applicable version (perhaps even =2.1-alpha.9 ; but at least 2.1- ). I had actually already changed this in my local script, but just forgot to paste it here in the forum. I've changed it. Another workar...

Example code: #Requires AutoHotkey v2.1-alpha M := Menu() M.Add("test", test) test(*) { return } AppsKey::M.Show(,, false) ; AppsKey::M.Show() Reproduction steps: Run example code Press AppsKey Click somewhere outside the menu Press AppsKey again On Windows 11, the menu is now behind all other windo...

OnMessage example doesn't support negative x, y coordinates Yes, because the example was added in 2005, when only one monitor was usually used and therefore negative coordinates were irrelevant. If you want this example to take this into account, you need to make a specific suggestion for improveme...

Thanks for reporting. I've fixed this.

Thanks for the clarification, @lexikos. I've removed it.

fixed

v2-Dokumentation an v2.0.13 angepasst.

Mehr Details auf GitHub

Ich habe es gefixt. Es muss this.Length sein, weil damit die Länge des Arrays vorab gesetzt wird.

Thanks for the suggestion. I've changed this.

v2-Dokumentation an v2.0.12 angepasst.

Mehr Details auf GitHub