programming in T.A.R.G.E.T (which uses C)

Don't ask me why, but I have two of these to use as dual sticks in games. It seems to have it's advantages. For one, I can program multiple things to happen on one axis. This give me a huge advantage in dogfights. Also I can program the entire keybord letters to my base buttons. No need for keybord...

But I lack the logic thinking to get my code completed.
I have multiple issues, and will adress them one at a time.

My first problem is my POV. That's the little mini thumbjoystick on top of a joystick for your Point of View camera ingame. The thing usually used for switching camera positions.

The trouble is this: In UPRIGHT position it executes both my UP and my RIGHT programmed stuff. Instead of a different third thing. My Conclusion is that UPRIGHT doens't exist as such, and Software just see that both UP and RIGHT are true, and execute code that says: When both are true, it's an in-between.
Works ingame, but I need a code that does something else.
'Cause Up might be 'missiles' , Right might be 'Start Chat', and I don't need missiles fired and chatting while doing UPRIGHT 'Dock to friendly Ship'

for short: I need a working code that says: When Up=True, and Right =True, both are not executed, and execute ActKey '2' (for example)

in my main file I got

Code:

MapKey(&T16001, H1U, Center_View);
MapKey(&T16001, H1R, View_Right);

In my ttm file (where my definitions are grabbed from) I came up with:

and I get '(' and ')' errors all the time about the first line. I tried adding and deleting '(' 's and ')' 's the whole time, and keep getting errors about them
Not sure when to use too, I tried these too.

I also have no idea if this is the code I am looking for to do what I need it to do. My study in C and TARGET doesn't give me enough clues about the correct syntaxis.

Been tinkering with learning T.A.R.G.E.T. and C code since november. And glad to say I got a lot of stuff already working .
It feels nice to have some skills you never thought you would ever aquire....

T.A.R.G.E.T. is software made by the Thrustmaster Joysticks. (the ones I use in the above)
I asked their helpdesk about helping me with code, but it seems they are non-existant. I get no replies on my emails, and other suffer the same faith... I got a mail last year that what I want can be done, but it was for advanced programing. And a 'good luck' to top it off... (is that a way to say: If you can do it...good for you?)

The program TARGET makes these additional files when compiling the lot for my joysticks to work.
(it makes one virtual joystick out of my two physical ones. A 'must' in some games, since they only want to see one joystick)
But alas... it only let's me use one of my two POV's, and I cannot seem to figure out why.
If anybody has got a clue how I can get my second POV active in the virtual joystick?

The comment behind some lines suggest it's ok for people to tinker with the code. Just be carefull with it when you do, it says on several places.

I already changed HAT (at the stGameCfg virtualj part) from 1 to 2 in both Hid.tmh, and target.tmh, in the hope I got my second POV HAT activated in the software. But alas...there seems to be more to it then just adjusting these two values... And I clearly lack skills here...

(Sorry in advance, I don't know how to embed code here)
Now, Direct X only recognizes a single hat, so what I had to do was map the second hat to keys.

I was wondering about that....Does this also apply if one has three or more Thrustmaster stuff USBed?
HOTAS and flightsticks also have hats, right? Only one of them all goes in Direct X?

I thought TARGET was flexible about using different stuff with it?

They (Thrustmaster) got weird logic anyway, lol...
Make ambidex joysticks, but make it hard in their software to use two of them?? Whatthe...?? It...just....makes...no... sense! And when people ask them about it...no updates in their software, manuals or not even replying to help out?? Now there's customer' faced for yah...

But if you're their underground customer service...nothing but thumbsup for you . You solved a major puzzelpiece.
You went code...