Hotkeys don't work in "Open" window of a paused script

[kidbit]

When you run a script that has a tray icon - you can right click that icon and select "Open" menuitem from the context menu (or just doubleclick the tray icon).
That will open a window which by default shows the recently executed lines in that script.
In that window if you hit the "View" menuitem in the menu bar you're going to see this:

As you can see - each menuitem has a hotkey, but they won't work if your script is paused or, say, stopped on a msgbox.
But you still can click that menuitem and that will work.
I don't know that's possible to fix (since ahk is a 1-threaded thing), I'm just reporting it.

[kidbit]

Also, it would be nice to have CTRL+A hotkey work as "Select all" there too (currently it doesn't, even when the script is not paused).

[RijulAhuja]

It seems to work fine, are you sure some other script is not interfering ?

[joedf]

1. When the script is paused, the code interpreter is also paused and therefore AutoHotkey is paused.
Clicking the menu item only launches a separate "thread" that is "not affected" by the current state of AutoHotkey.
Note: Labels can still be launched even if AutoHotkey is paused. This is where A_IsPaused comes in.

A script is always halted (though not officially paused) while it is displaying any kind of menu (tray menu, menu bar, GUI context menu, etc.)

see http://ahkscript.org/docs/commands/Pause.htm and http://ahkscript.org/docs/misc/Threads.htm for more info on that.

2. basically it is like an edit control with the following tags "+ReadOnly -WantCtrlA"
see http://ahkscript.org/docs/commands/GuiControls.htm#Edit

Regards, no bugs

[kidbit]

Regards, no bugs

No, it's a bug. You just explained the reasons why it exists.

I think AHK should always assign an additional thread just to serve that built-in menu, that could be open for every AHK script.
However, I don't have any hopes that Lexikos will ever fix this bug.

[joedf]

it's a Microsoft Windows quirk, not an AutoHotkey bug...

[lexikos]

joedf's explanation of the cause is totally wrong. The problem is that the menu shortcut keys are implemented by the program's main message loop, which isn't running while a MsgBox is visible. It's been a known issue for nearly ten years, and yet there are very few complaints.

[joedf]

Oh right! Whoops, I'm sorry for the confusion here

[Nextron]

The problem is that the menu shortcut keys are implemented by the program's main message loop, which isn't running while a MsgBox is visible.

Does that same reason apply to this effect:

A script is always halted (though not officially paused) while it is displaying any kind of menu (tray menu, menu bar, GUI context menu, etc.)

Because that is somewhat annoying too.

[lexikos]

Yes

[joedf]

Well it must be difficult for one person to use 2 brains at the same time