TM Warthog - multiple keys bound to button?

[AbortedMan]

Hi all, new Warthog owner here, getting my config just right in TARGET (not using the default plug and play as I want my own button mappings) I'm trying to bind a throttle button to a combination of keyboard buttons (Left arrow x3), but for the life of me cannot figure it out. All I can get TARGET to do is create a sequence of bound buttons that activate the next on each subsequent pressing of the assigned throttle button.

 

Is TARGET completely incapable of creating a true macro? Or am I missing something completely obvious?

 

Any help would be greatly appreciated.

[cichlidfan]

You want to use the CHAIN function instead of the SEQ function.

[AbortedMan]

You want to use the CHAIN function instead of the SEQ function.

 

Couldn't find a "CHAIN" function within TARGET, but I realized I needed to configure delays (20ms each, so 1st LARROW - no delay, 2nd LARROW 20ms delay, 3rd LARROW 40ms delay, etc) between the button assignments to accomplish what I was doing. Silly me.

 

Problem fixed. Thanks for the reply.

 

Now I'd like to figure out how to configure an ongoing chain that doesn't stop until I release without having to create hundreds (actually, infinite) of new assignments with corresponding delays manually...

[cichlidfan]

Have you looked at the Target Scripting manual?

 

From page 24:

CHAIN function: Generating events at the same time

CHAIN is the command that gives you the ability to have multiple outputs by pressing a button once. CHAIN

provides more possibilities than just generating several events on one action; it also defines the timing of those

events with the Delay and Lock commands (please see further along in this manual for more details).

CHAIN(PULSE+'a', PULSE+ 'b') //this chain generates “a” and “b” momentary keystrokes.

 

Let’s place our CHAIN into a MapKey function.

 

Syntax:

MapKey(&Device, button name, CHAIN(event 1, event2,…)

 

Example:

MapKey(&Joystick, H3U, CHAIN(PULSE+'a', PULSE+ 'b')); // When I press the Hat 3 Up direction on the joystick,

“a” and “b” are going to be pulsed.

If you test this line with the Event Tester software, you will notice that:

 

 “a” and “b” are pressed at the same time, then released together. This means that if you use several

combo keystrokes in your CHAIN, they will be mixed up. To avoid this, use the Delay (see later).

 

 If you remove the PULSE for the b keystroke and still hold the HAT3 button Up, “b” will be held until you

release the button. To avoid key holding, you can simply use the PULSE+ command.

[AbortedMan]

Have you looked at the Target Scripting manual?

 

From page 24:

 

Aww man, user fail. I'm usually not ever one of "those guys". Right in front of my face. Thanks.

[cichlidfan]

Aww man, user fail. I'm usually not ever one of "those guys". Right in front of my face. Thanks.

 

No problem. :)