Bug?: DirectX Assignment behaves differently to Keyboard assignment.
-
Hey all
Has anyone come across this issue and has a solution for it?
I want to assign (for example) the equivalent of the Tower callback to a DirectX button. But it behaves differently to a keyboard key.
If I press “T” on my keyboard, the Tower menu comes up, and stays up, and as I press and release the “T” key the different sub pages appear.If I try to replicate this with DirectX programming, it doesn’t work. Pressing the DirectX button displays the Tower menu and it stays up. Pressing it again, the Tower menu disappears. I can’t cycle through the sub pages.
The programming I’m using is:RadioTowerCommand 192 -1 -2 0 0x0 0
I’ve tried the various options for the 3rd and 5th section of the statement with no success. Is this a bug or am I missing something?
Cheers
James
-
This is not a bug.
Use one of these:
OTWRadioMenuStep
OTWRadioMenuStepBack
RadioMenuOne
RadioMenuTwo
…
RadioMenuNine -
Hey Kolbe
Many thanks for getting back to me. Using OTWRadioMenuStep and OTWRadioMenuStepBack work well to step through the menu pages - thanks.
Ideally I’d prefer not to tie up another 2 physical buttons for this, but instead have RadioTowerCommand DX assignment behave exactly as the keyboard assignment. If you can mention it (I understand it woudn’t be a priority) on the Dev forums that would be cool. They may not realise they behave differently.Thanks again for taking the time to reply.
Cheers
James
-
Hi James,
in fact, it works exactly that way.
Let’s have a look at the corresponding key file content:RadioMessageSend -1 0 0x14 0 0XFFFFFFFF 0 -2 "Radio-send message ATC" OTWRadioMenuStep -1 0 0x14 0 0x14 1 -2 "Radio-Next Menu ATC" OTWRadioMenuStep -1 0 0x14 0 0x14 0 -2 "Radio-Next Menu ATC" OTWRadioMenuStepBack -1 0 0x14 1 0x14 1 -2 "Radio-Previous Menu ATC" OTWRadioMenuStepBack -1 0 0x14 1 0x14 0 -2 "Radio-Previous Menu ATC"
As you can see the code uses exactly the same callbacks. So, pressing “T” multiple
times steps through the pages because the code invokes OTWRadioMenuStep.
On the other hand, I think there was an issue with “Shift T”, which should step back.
I think this doesn’t work. But I’m not sure.Bottom line, the code is designed that way.
I could ask if someone would be so kind to change the DX behavior of Step / Step back.
Don’t hold your breath.