This is driving me past distraction! I would greatly appreciate it if someone would try this code and tell me if this is a bug.
In this code, test_trig1 works as expected (it doesn't display 'no match' when enter, space or tab is used), but test_trig2 gives 'no match'.
Code:
; proof of concept, can i simulate a non-auto hotstring for each of the shortcut triggers
; space, tab, enter
; check the value of a_endchar before doing the action
msgbox, Type`ntest_trig1{endchar of your choice: enter, period, space, tab, etc}`nor`ntest_trig2{endchar of your choice: enter, period, space, tab, etc}
:O:test_trig1:: ; without b0 a_endchar is set correctly
:b0O:test_trig2:: ; the b0 causes a_endchar to not be set
l := strlen(a_endchar)
send, len=%l% a_EndChar=
if a_EndChar = `n
{
send, enter
}
else if a_endchar = %a_tab%
{
send, tab
}
else if a_endchar = %a_space%
{
send, space
}
else send, no match %a_endchar%
return
After reading the help file I would expect exactly the opposite results, though I would still consider it a bug. The help file states that the only time that a_endchar is blank is if the * option is used.
Can this be added as a needed
code change to AutoHotkey?
Thank you.[/b]
Login
Register
FAQ
Search
