I don't use Client-Server so I can't help with that. But it works with any game 'at all', then TB must be setup correctly. The issue must be with a specific profile....
Do you have to press and 'hold' the Shift+Numpad7 key to move the trim in the game? I'm guessing yes. If that is the case, then just using a normal button won't work. You should use a 'Touch' type button probably. Read in the Toolkit Help file about the button types.
A normal 'button' type button, only sends the keystroke once. If you need to hold a button down for a period of time, you have several options. For this Trim stuff I would look at using the 'Touch' type buttons first. Also maybe a 'Hold' type button.
Also, you could code a 'Hold' type button's macro like this:
Code:
macro_select = predef:SHIFT, KEYDOWN
macro_select = predef:NUMPAD7, KEYDOWN
macro_deselect = predef:NUMPAD7, KEYUP
macro_deselect = predef:SHIFT, KEYUP
With this Hold Button, the first time you touch the button, the Shift+Numpad7 keys will be press down (KEYDOWN) and held in the downstate.... until... You touch the button again, which sends the Shift+Numpad7 'KEYUP' command, thus releasing the keys. Probably not what you want for Trim, but a good trick to know. I use this to hold my 'B' key down in IL2 for my Wheel Brakes. But read up on this KEYDOWN/KEYUP in the help file. If you exit TouchBuddy, or your game while any key is left in the down state, Windows will think you are holding those keys down on your keyboard and it will go bonkers....
WBK