AlomWare Toolbox Forum

General Category => General Discussion => Topic started by: oblivion on May 29, 2026, 01:14:04 AM

Title: Hotkey oddity
Post by: oblivion on May 29, 2026, 01:14:04 AM
I finally allowed my laptop to update to Windows 11 25H2 today, on the basis that most of the issues with it are either ironed out or good workarounds exist. In fact, I have so many customisations in place that, at least superficially, I can't see a difference between it and 24H2.

But. I have a tiny action that opens Toolbox at the Automation tab (with ctrl-shift-A as the hotkey) instead of my usual default, for when I'm creating new Actions, and although I'd created a placeholder for my text case action, I hadn't written it yet. 

So, update completed, I hit ctrl-shift-a to open Toolbox Automation and it didn't work.

Oh. The Toolbox icon in the notification area had gone away. Weird. Run Toolbox back up and I went to check that the action wasn't using a hotkey that the updated version of Windows had reserved for something new.

Clicked the "set trigger" button and, sure enough, Toolbox is telling me that that combo isn't available anymore. And although I could set other triggers, I found myself wondering if I'd lost any others.

Quite a few, it turned out.

But then, instead of using the "set trigger" button to set a new trigger, I hit the "delete trigger" button and, having done so, found that I could set a new trigger of ctrl-shift-a without an issue -- in other words, there was an issue with the chosen trigger but deleting it and replacing it with the same trigger put it back how it was.

Is this a real bug? Dunno. Is it Windows' fault? Maybe. But I thought I'd post it here in case it bites anyone else...
Title: Re: Hotkey oddity
Post by: Paul (Lead Developer) on May 29, 2026, 10:30:00 PM
I moved this topic to "General Discussion" because I don't think it's a Toolbox bug. It sounds more like a one-time glitch of something with Toolbox and your Windows update at the time. But if the problem can be repeatedly reproduced with instructions for me to follow, then I'll happily look into it as a bug.

BTW, Toolbox "resets" its trigger list when you refresh the Action list (like when holding down the Ctrl key and clicking the list header). Any clashing triggers will be shown in red.
Title: Re: Hotkey oddity
Post by: oblivion on May 30, 2026, 10:50:09 PM
If you think I'm going to roll back to 24H2 (I do have a full backup, I could, but argh) you have another think coming. :D

The refresh trigger list: yes, that's a useful thing to know, I'll try to remember that.

By the way, I just spotted the move to numpad# option for windows and mouse movements (in your Toolbox vs Autohotkey comparison post) and yay! Is that newish, or is it just one of the (many!) things in Toolbox I'd failed to notice / register when I was writing things?

At a tangent: the comparison between Autohotkey and Toolbox is interesting and useful. I'd also add that Toolbox scripts mostly don't need to be completely rewritten when there's a Toolbox version change -- I have an extremely complex Autohotkey script at work that operates as an automation robot: takes data from one source and copies it to another, in the absence of a "proper" backend interface. It was written in Autohotkey v1 and fails so hard in Autohotkey v2 it'd make your head spin. :D
Title: Re: Hotkey oddity
Post by: Paul (Lead Developer) on May 31, 2026, 01:12:57 PM
The "numpad#" trick has been there since the beginning. :)

Also for resizing a window, you can specify "numpad3" to resize the window to the bottom-third of the desktop, or as "numpad5" to center it in the middle of the desktop, and even as "numpad46" to resize it as a strip across the middle-third of the desktop (since keys 4 to 6 are across the middle of the numeric keypad).