~LWin Up blocked

[RobertL]

~LWin Up::return nor ~*LWin Up::return can open the "start" button when release.
1.1.22.09 Win7 64bit AHK 64bit

[lexikos]

It blocks the start menu but does not block the key-down or key-up. This is intentional/by design, and also applies to the Alt keys.

[RobertL]

So, ~ is not necessary here, and could use $LWin Up::Send {LWin up} instead?

[lexikos]

No...

[RobertL]

Currently, I Send {Lwin} in ~LWin Up:: to open start menu. Although don't know the effect of ~ here.

[lexikos]

LWin up:: will block the key-up event. It will also block the key-down event if you don't have ~LWin::. This will prevent you from using LWin to activate system hotkeys, like LWin+E for Explorer. As I said, ~LWin up::return does not.

Send {LWin} sends key-down and key-up without any intervening keystrokes, so is different to Send {LWin up}.

[RobertL]

Strange, ~LWin Up::return or ~*LWin Up::return now can open the "start" button. I can't reproduce the error.

LWin up:: will block the key-up event. It will also block the key-down event if you don't have ~LWin::

is unexpected comprehend, be it so.

Thank you.

[lexikos]

is unexpected

Why? Didn't you read the manual?

An "Up" hotkey without a normal/down counterpart hotkey will completely take over that key to prevent it from getting stuck down. One way to prevent this is to add a tilde prefix (e.g. ~LControl up::)
Source: Hotkeys (Mouse, Joystick and Keyboard Shortcuts)

It works both ways; key:: also blocks the key-up event.

[RobertL]

I found my problem, code above is incomplete, should be: asterisk is option

Code: Select all

~*LWin::
~*LWin Up::return

will block start menu. I think Up is stand alone, so didn't metion key-down, which is there and take effect.

is unexpected

because the independence I conceived. Thank you for pointing that section on manual
I'm not sure if these case exists and be considered: LWin is put down by send or set only LWin up by Hotkey after down was pressing, where there is no LWin down hotkey.