Different register in A_ThisHotkey

[serzh82saratov]

This is the same as in GetKeyName, in the header register. If you uncomment ~$uP ::, then another hotkey is specified.
Can you make a correction, A_ThisHotkey is always identical to GetKeyName?
Or, at least, stayed, in the form in which he was appointed for this label.

Code: Select all

Hotkey, % GetKeyName("uP"), Lbl
SendLevel, 100
Send {up}
Return

Lbl:
	MsgBox % A_ThisHotkey
	Return
	
; ~$uP::Return

[Helgef]

This is documented behaviour,

When a hotkey is first created -- either by the Hotkey command or a double-colon label in the script -- its key name and the ordering of its modifier symbols becomes the permanent name of that hotkey, shared by all variants of the hotkey.

Maybe you mean for this to be in the wish list forum?

Cheers.

[serzh82saratov]

Then yes.

[jeeswg]

For situations like this I often create multiple labels pointing to the same code, and check A_ThisLabel.

[lexikos]

Can you make a correction, A_ThisHotkey is always identical to GetKeyName?

No. Then the names of individual hotkeys would unexpectedly differ from what the user wrote in the script, and scripts relying on the documented behaviour would no longer work.

The "canonical" name returned by GetKeyName might not be what the user expects (with respect to keys with multiple names). Hotkeys specified by VK or SC behave differently in some cases than those specified by name, but GetKeyName always returns a name. The presence and order of modifier symbols can vary. Using the first name and ordering found in the script is best overall.