AutoHotkey Community

hit 'c' or 'd', get 'aXYZ'; why not 'ab'? If SendRaw does not do that, what does? In other words, how to output a char 'as is' without having it reinterpreted through hotkeys?
hitting 'e' does nothing; why?

Use the $ modifier.

_________________
GitHub • Scripts • IronAHK • Contact by email not private message.

Thank you! However, I ran into some weird behaviour:


hitting e gives bUVW --OK; but so does hitting c or d!

If you read the link Titan provided it will tell you what the $ prefix is for:

_________________

Try Quick Search for Autohotkey or see the tutorial for newbies.

Not true. I tried it:
Hit a, get UVW
Hit b, get XYZ
Hit c, get UVWXYZ not ab
Hit d, get UVWXYZ not ab
And you don't explain why, in the script I used, hitting 'c' or 'd' gives 'bUVW' instead of the expected 'UVWb'

Are you using the most recent version of AutoHotkey? I tested that script before I posted it so I know that it works.

_________________

Try Quick Search for Autohotkey or see the tutorial for newbies.

Where to find the version number?

Hover your mouse over the exe file itself, it should bring up a tooltip with the file version.

_________________

Try Quick Search for Autohotkey or see the tutorial for newbies.

OK: 1.0.48.5

...I tested your script & I got the same behavior as TAB4217, the wrong behavior...this works tho...


...this works too...


...you must enable the hook on the Hotkeys you don't want simulatable (simulatable?), in this case you want to send a & b & not have them re-simulated as the other keys, so at a minimum enable hook ($ prefix) on a & b...or #UseHook on all keys so you don't have to worry about which ones to $ later...

Yes! TY. Boy, is AHK complexe... and unintuitive!
Now, my other question:

hitting e gives bUVW --OK; but so does hitting c or d, which should give UVWb. Why?
And, why does hitting 'z' do nothing?

You really don't need to quote so much of each post when replying...


...complex, yes, but I think it's completely intuitive for Send, ab to give UVWXYZ when the simulated keys are stacked (SendRaw is not designed for this purpose)...


...(z was not part of this other question before now)...but I believe it's a bug...or at least THIS is unintuitive...you must sleep between keys, not sure why...


...Sleep, 0 is enough for c to work, Sleep, 28 works on my comp for SendInput (0 & 19 are not enough)...the above requires my Send() function...or broken down ugly code...


...the z key works for me in notepad...(it sends ab)...

OK; I was referring to the effect of #UseHook.

It was 'e' in previous post --2010 Feb Mon 22, 11:20 am

AHK did not recognize the 'function' Send; so, I removed the parentheses, and got:
c-> "b"UVW
d-> "b"UVW
The quotes being unwanted, I tried

and obtained:
c-> bUVW
d-> b, "Input"UVW
I don't understand what ', "Input"' is supposed to do; so I removed it: both 'c' and 'd' yielded 'bUVW'. The mystery remains: why 'ab' reacts like 'ba'.

...narf!...I said...


...my Send() function allows "sleeping inside a send", which is why I used it...


...it don't matter what you got when you removed the parens, my Send() function is a function & needs parens...


...my 2nd example DID NOT require my Send() function & DOES provide your wanted output...however, why sleeping between keys is necessary does remain a mystery tho...