lu0 / autohotkey-config Goto Github PK

Auto-rotation stops working altogether if the rotation lock feature is manually modified in Windows' settings (bug?)

Originally posted by @lu0 in #8 (comment)

The screenshots.exe script suddenly dies, it may die after a couple of minutes or even hours. Haven't found the issue, yet.

Sometimes the hotkeys just... break, as if I was pressing ctrl + alt. I "fix" this behaviour with ctrl + alt + del, then press CapsLock two times (mapped to Esc) and then Esc (mapped to CapsLock).

I don't know why this is happening, yet.

Distinguish "copied to clipboard" (CTC) screenshots from regular screenshots, maybe by storing CTC screenshots in a subfolder of screenshots-ahk, thus avoiding clutter.

Describe the bug
Keybindings do not work if the active window or dialog is a privileged one (owned by the administrator); i.e. Admin terminal, admin powershell, task manager, installation dialogs, etc.

Wanted to brush it off, but it's frustrating me. Put here so that I don't forget.

To Reproduce
Steps to reproduce the behavior:

1. Open any program as "Administrator".
2. Try to trigger any autohotkey script.
3. The script / keybinding won't do anything.

Expected behavior
Scripts should be triggered on any type of window and dialog.

Screenshots
n/a

Desktop (please complete the following information):

• OS and build: Windows 10
• Autohotkey version: 1.1.33.10
• Repository version: Latest

Additional context
n/a

Steps to reproduce:

• Open a Terminal in Workspace 4.
• Don't hide/minimize it (don't trigger keybinding Meta + Return).
• Switch to Workspace 1.
• Try to unhide/raise the existing terminal (keybinding Meta + Return).

Output:

• Neither the existing Terminal nor a new one is raised.

Desired output:

• The existing terminal should be raised in the active Workspace regardless of the Workspace it is placed in.

This is triggered when we have +2 windows in the same Display and cycle with the default keybinding.

This behavior gets specially annoying when we want to be able to see the contents of the window we cycled from if the dimensions of the window we are cycling to allows it.

I don't have the time to debug it right now; I'm storing it here as an issue as I tend to forget this kind of things, until the behavior gets in my way again :)))))

Describe the bug
When using the area capture feature (Win+Shift+PrtScr) in the script, it cycles through all system cursors instead of consistently displaying the plus (+) cursor while the hotkey is held down.

Additionally, once the hotkey is released, the cursor becomes static on the last cursor in the cycle, instead of consistently showing the plus (+) cursor.

To Reproduce
Steps to reproduce the behavior:

1. The script is running.
2. Press the keybinding Win+Shift+PrtScr to trigger captureArea
3. The script starts cycling through different cursors instead of showing the '+' cursor consistently. The '+' cursor appears only when the current cursor is the normal arrow mouse, and other cursors are shown when the current cursor is different.

Expected behavior
The cursor should consistently remain as a '+' during both the holding of the hotkey and the selection of the capture area.

Desktop:

• OS and build: Windows 11 (various builds)
• Autohotkey version: 1.1.33.10
• Repository version: f8484ca