Interpreting KeyIdentifier and EventIdentifier values in hotkeys.ini

[BallisticBuddha]

Hey all, I'm sorry if this might have been asked before, but I really cannot seem to find an answer to this anywhere, but anyway.

TS3 keeps a configuration file (named hotkeys.ini) within the Roaming AppData folder in Windows 7. I was informed that this is where you can manually edit your hotkeys if setting it within the client does not seem to work. My end goal is to set my Push-to-talk key to F18, and to have a truly dedicated PTT key that serves no other function with any other application. Yes, I know, that key does not exist on most current keyboards, however it is still interpreted as a valid keypress in Windows. The reason I wish to set it as such is because I have a mouse (Corsair M90) that supports macro keys buttons. I manually edited one of the buttons (by exporting profiles, editing the binding values in the .xml file, and importing them) to act as F18. I then saved the profiles to the mouse (for hardware playback) and now it seems to work properly and recognize the button as F18.

Now I am trying to modify my TS3 client to change my PTT key to F18 but am having issues. First, I tried just pressing the newly configure mouse button, but that didn't work (as it normally doesn't with my mouse's macros, as previously I had PTT bound to "ctrl+/", and had to manually enter that key combo). Next, I found out about the hotkeys.ini file where you can manually alter these values. I first set my PTT key to F12, and am trying to find out how to change it to F18.

Here is my current hotkeys.ini (with PTT set as F12):

[Profiles]
Hotkeys\Default\Bindings\size=2
Hotkeys\Default\isDefaultProfile=true
Hotkeys\Default\Bindings\1\Event\Type=1
Hotkeys\Default\Bindings\1\Event\Mode=Down
Hotkeys\Default\Bindings\1\Event\Key1=F12
Hotkeys\Default\Bindings\1\Event\KeyIdentifier1=1864182625-54688-4559-191-199-68-69-83-84-0-088
Hotkeys\Default\Bindings\1\Event\EventIdentifier={480a1ebe-1611-4af3-a246-51e34f67c43e}
Hotkeys\Default\Bindings\1\Action\Type=320
Hotkeys\Default\Bindings\1\Action\Mode=Activate
Hotkeys\Default\Bindings\1\Action\Profile=Default
Hotkeys\Default\Bindings\1\Action\Description=Activate Push-to-Talk
Hotkeys\Default\Bindings\1\Action\Auto=true
Hotkeys\Default\Bindings\2\Event\Type=1
Hotkeys\Default\Bindings\2\Event\Mode=Up
Hotkeys\Default\Bindings\2\Event\Key1=F12
Hotkeys\Default\Bindings\2\Event\KeyIdentifier1=1864182625-54688-4559-191-199-68-69-83-84-0-088
Hotkeys\Default\Bindings\2\Event\EventIdentifier={3ceb8cab-c417-419c-8419-c0106ac31cb1}
Hotkeys\Default\Bindings\2\Action\Type=320
Hotkeys\Default\Bindings\2\Action\Mode=Deactivate
Hotkeys\Default\Bindings\2\Action\Profile=Default
Hotkeys\Default\Bindings\2\Action\Description=Deactivate Push-to-Talk
Hotkeys\Default\Bindings\2\Action\Auto=true

There are variables for Key1, which apparently is just a label, as I changed that to F18, but now it just says that my PTT is F18, but it still functions as F12 after changing those variables.

Next, I realized the lines:
Hotkeys\Default\Bindings\1\Event\KeyIdentifier1=18 64182625-54688-4559-191-199-68-69-83-84-0-088
Hotkeys\Default\Bindings\1\Event\EventIdentifier={ 480a1ebe-1611-4af3-a246-51e34f67c43e}

Hotkeys\Default\Bindings\2\Event\KeyIdentifier1=18 64182625-54688-4559-191-199-68-69-83-84-0-088
Hotkeys\Default\Bindings\2\Event\EventIdentifier={ 3ceb8cab-c417-419c-8419-c0106ac31cb1}

and looked online for other examples and I realized that every example I could find had their KeyIdentifier1 variable that looked exactly the same as mine, except for the last bit (where mine is 088). So, I inferred simple induction at that point and tried changing the 088 to 096 (6 higher than 088 in decimal), because this is how I got it to work with the Corsair profiling software (except the values were in hex). However, that didn't work. Now my PTT key doesn't work as F12 or my falsified F18 keypress, so I'm not sure what key 096 is referring to. I can't seem to find out anywhere, as I've been searching for the past couple days, how these variables translate to keys.

So, my primary question is if anyone here knows how to interpret these values so I can manually change my PTT key to F18?

Any help would be much appreciated

[SilentStorm]

Thats because Key 96 is actually the ` Key, but then again F12 is 123 in decimal.

Microsoft defines F18 as #define VK_F18 0x81 which is 129 in decimal. But then Microsoft has 96 decimal (0x60) as VK_NUMPAD0...

Don't know but it doesn't seem that the 088 you found to be the actual key is the value for the key and if it is it's went through some sort of conversion.

On a second thought... since TS3 uses Qt they might be using Qt's Key Definitions

[BallisticBuddha]

Thanks for the info, but I still can't seem to find any values that work, the Qt definitions don't seem to represent the KeyIdentifier directly.

I'm currently trying to find another way to input F18 without using the mouse so that the TS client can recieve the input properly, but haven't found a way yet.