stacked hotstrings with X execute option (v1 to v2 changes)
Posted: 19 Jun 2023, 09:34
In v1 there are two ways to stack execute hotstrings to perform the same execution
and
In v2 only the second way works. The first way throws "Error: Expected single-line action" at the first line.
Is there some way to get the first way working in v2?
@lexikos is this v1/v2 difference intended? I think a benefit of the first way is that the explicit X on each line serves as a visual reminder (when later reading the code) that each stacked hotstring will use the execute option.
Some background: The v2.0.2 hotstrings doc pages doesn't mention stacking in v1 or v2 so it is unclear if this is even an intended use case. But such stacking has de facto worked for a long time in v1. In contrast for hotkeys v1 and v2 documents that "Multiple hotkeys can be stacked vertically to have them perform the same action."
Code: Select all
:X:b::
:X:c:: MsgBox 123
Esc:: ExitApp
Code: Select all
::b::
:X:c:: MsgBox 123
Esc:: ExitApp
Is there some way to get the first way working in v2?
@lexikos is this v1/v2 difference intended? I think a benefit of the first way is that the explicit X on each line serves as a visual reminder (when later reading the code) that each stacked hotstring will use the execute option.
Some background: The v2.0.2 hotstrings doc pages doesn't mention stacking in v1 or v2 so it is unclear if this is even an intended use case. But such stacking has de facto worked for a long time in v1. In contrast for hotkeys v1 and v2 documents that "Multiple hotkeys can be stacked vertically to have them perform the same action."