AutoHotkey Community

Fixed by v2.0.15.

You do not need to "trace every instance of SetCapsLockState". Off the top of my head, you could: Define your own MySetCapsLockState function and use search and replace to replace calls in your script, no "tracing" needed. Your function can call the built-in one before/after recording whether the Al...

If you must ask "is this a bug?", it likely isn't. Please post in Ask for Help in future. I have moved the topic. When you omit the L option, KeyWait will wait until the key is not being physically pressed down. You are not physically pressing down LCtrl or F14, so it does not wait. If you use the L...

Fixed DBGp property_get failing to retrieve properties due to incorrect paging (since v2.0.14). Fixed DBGp property evaluation causing Try without Catch to fail (since v2.0.14). Fixed <base> debugger pseudo-property leaking a reference (since v2.0.14). 207FEA03708F1BA8C8E61F30170D799495736726D1853D7...

ToolTip currently uses whatever default font Microsoft gave the ToolTip control. AutoHotkey does not set it. It would be possible, but would have to be opt-in somehow, as changes to default tooltip size could break some scripts. GUI does not respond to TextScaleFactor at all as far as I can tell. I ...

Again, it's not really about whether it's a bug or not All I said on that note was "This is not a bug." Whatever you think "it" to be about, this was about the issue you presented and its placement in the Bug Reports forum. Practical reasons for or against changes aren't about whether it's a bug or...

This is by design, so I have moved the topic out of Bug Reports. Also note that no one is maintaining v1.1. See End of Life: v1.1 . RShift is released immediately, but it is not by send {sc036 up} . You can confirm that KeyWait is not returning early by checking ListLines or KeyHistory, or by adding...

Retrieving the name of a process the direct way (i.e. without enumerating all processes) requires the PROCESS_QUERY_LIMITED_INFORMATION access right to the process. If you are denied access, you get an error by design. This is not a bug. Are there any cases where the existence of a window belonging ...

Slight correction: v2.1-alpha.5 and later support remapping to/from the wheel.

That has never been valid/supported. The following keys are not supported by the built-in remapping method: The mouse wheel (WheelUp/Down/Left/Right). Source: Remapping Keys (Keyboard, Mouse and Controller) | AutoHotkey v2 Use Send, so they will be hotkeys, not remapping. XButton1 & WheelUp::Send "{...

Removing a thing which is already implemented, guaranteed by documentation and has been used for 20 years is quite different to doing nothing; i.e. not implementing a new function.

But I do not want Alt to be pressed down again. Why not? If you press LAlt+w twice in a row without releasing LAlt, it will not work the second time if LAlt has been released by Send and not "pressed down again". This is what Send does with physical keys when you do not use Blind, or when you exclu...

I didn't take the time to reply because the reason I opened the forum was to release v2.1-alpha.10. ;) Seriously though, there are only so many hours in the day. It takes time to document changes, even just bug-fixes, and make the release actually work. For v2.0.13, there was a sequence of last-minu...

It can be done with a simple one-liner. Why should the interpreter and documentation be inflated with these small but completely redundant functions? For matters of convenience, there are solutions that don't involve adding more redundant built-in functions, or waiting for someone else to do it for ...

Fixed by v2.0.14 (documentation for #1, behaviour for #2).

Fixed by v2.0.14.

Fixed by v2.0.14.

The unintended integer return is fixed by v2.0.14.

The return value is intentionally still unspecified.