evilC wrote:AFAIK F13 is technically CTRL+F1
Did you try making sure the key got held for a certain amount of time? That might force it to recognize the key
Code: Select all
SetKeyDelay, 0, 50
F12::
Sleep 2000
Send {F13}
return
I don't see the use in using AHK to convert CTRL+F1 to F13? If other apps do not respond to F13, what use will that be?
Surely you just need it as a "Transport Key" so that buttons on your keyboard can trigger AHK code?
I may try to explain better, maybe i'm explaining it the wrong way.
- SteelSeries APEX keyboard have many extra keys so we can create macros for them using the SS Engine software
- The SS engine, which handles all the keyboard functions, doesn't recognize the F13-F24 keys, I already researched about this, that's why sending an F13 to the SS Engine keyboard macro editor doesn't work. If I use the same exact code you suggested to make F12 send a F5 for example, it works, to F12 send and F13, it stays empty as nothing was pressed. Logitech has a different engine and while it doesn't lists F13-F24, it recognizes it if sent to it like you did.
- Softwares recognize F13-F24, but some softwares I use do not accept keystrokes, only one key as shortcut, and some games also accept only 2 keys, not 3.
- So on the SS Engine macro keys I'm for example sending from M1 RControl + F1, and then trying to use AHK to convert this to F13, which didn't worked with neither codes I tried above.
Is it more clear?
Thanks!