Can anyone direct me to documentation on using Action Mapping via MDX in the latest release of the DX9 SDK (Feb) Searching has proved mostly fruitless and DX8 samples of AM (using DIACTION, etc) are useless as it appears the entire structure has changed. I've looked through the SDK docs but they are simply a shell outline and only list classes and their members - there is little to nothing in the way of description and zero examples.
Also, are VB docs and coding examples for any of DX planned As a VB.NET coder I feel like the "forgotten stepchild" when it comes to DX as the majority of the material is in C++ or C# (actually 100% of the new stuff).
Thanks,
Scott
MDX2 and Action Mapping?
Del Robinson
The correct starting point for beta newsgroups is http://msdn.com/directx/beta.
And we prefer to spell it "Center"
Astral
Yes Joysticks are the last big domain of DirectInput. As I know some flight simmers I suggest that you allow to map keyboard events to actions too because some have special hardware that inject keyboard commands.
If you need only mouse input use the default windows messaging as DirectInput use it internal anyway.
topcaser
Thanks for the fast reply!
I am going to be working almost exclusively with joystick input for flight simulation programs, hence the use of DI. Eventually I will probably migrate to my own custom hardware but for now will be using standard joystick input. I can bypass action mapping and create my own scheme for accepting and storing user mappings.
Another application will require mouse input - user clicking on specific areas of a bitmap displayed on a form. You are suggesting I avoid using DI for this and simply utilize stock Windows mouse events
Thanks,
Scott
Mike Wilson
As the system is still in beta you should be posting questions like this in the public beta newsgroups, you can sign up for these through the Microsoft DirectX Developer Centre.
On another note I have updated my Documentation file for the Lib's on my blog.
mbaluyos
I cannot offer you a documentation but I would suggest to stay away from Action Mapping. It was never very popular as the standard Action Mapping UI does not fit very well with game UI. But the main reason is that it is not longer recommended to use DirectInput for mouse and keyboard input. You should use the default window messages for this. Additional the new Xbox 360 controller has with XInput an own API that does not support something like Action Mapping. In summary you will need your own mapping system anyway.
Twawsicoa and zman have converted some of the SDK samples to VB.Net. Have a look: http://www.thezbuffer.com/articles/187.aspx