AutoHotkey Community

Tested with v1.0.40.05:

;::X ; doesn't work
`;::X ; doesn't work
X::; ; doesn't work
X::`; ; doesn't work
Semicolon::X ; doesn't work (this would be the easiest solution to implement)
X::Semicolon ; doesn't work
SC027::X ; this works but it isn't very intuitive
X::SC027 ; but this doesn't work

Previous thread: http://www.autohotkey.com/forum/viewtopic.php?t=3619

This works. Tested with AHk v1.0.40.05 on Windows XP SP2.

I characterized the other combinations:

* <Shift> (aka, +) combinations produce wrong output
* X produces wrong output in all cases

Update: I got these to work after switching the default keyboard layout in the control panel.
x::`;
`;::x

There's a subtle bug that only happens when the current layout isn't also set as the default layout.

I'll try to post soon the steps to reproduce the problem.

If the script's keyboard layout doesn't match that of the active window, problems may occur with the Send command and Hotstrings. UPDATE: Hopefully this issue is no longer present in newer versions. If anyone has any trouble with it, please let me know.

If you mean there's something that should be considered a bug, I could use more details. I tried the examples you gave and they seem to work as expected on my system (at least if you consider that each remapping is translated into a pair of Send {Blind} hotkeys as described on the remapping page). But maybe that approach is too simple/limited to cover all possible remappings.

I have posted the code I tested with and the results for each input. For example:



There is an apparent discrepancy between the way the semicolon is handled when the Shift is depressed simultaneously or the Caps Lock is toggled on.



The problem here is the : (colon) output when pressing Shift and x.

I decided to have the program implement each remapping as a pair of hotkeys, which has its drawbacks. Within the limits of the design, I think the above is normal behavior.

I think this is normal if you read between the lines in Send {Blind}, which states, "{Blind} also causes SetStoreCapslockMode to be ignored". I know it's not well documented because someone would have to go from the remapping page to the Send page then to the SetStoreCapslockMode page, put all the pieces together, and only then might it become clear. However, the documentation is already long enough that people are discouraged from reading it, so it is my judgment that rare issues like this should not be explicitly documented (in this case, I think it's a rare issue because remapping to an uppercase character or to a punctuation character is somewhat unusual).

Although I think everything is explained by the limitations of the remapping feature, if you see something that still seems too misleading or incorrect, I can try to update the program or documentation.

Thanks.

No. That will not be necessary.

This has not been an issue for me. The only reason I posted, was to explain or describe the apparent issues observed by Guest.

You'd might want to update the FAQ so that it also mentions key-mapping.