Author Topic: dinput.h for GoAsm?  (Read 2837 times)

satpro

  • Member
  • **
  • Posts: 116
dinput.h for GoAsm?
« on: January 21, 2014, 06:28:59 PM »
Just a quick question.  Do we (or does anybody) have the dinput.h (dinput8.h?) header for DirectInput?  I suppose I could hand-code or use XlatHinc, but I'm a bit uncertain how to use that program, not completely understanding everything it puts out.

Thank you.

wjr

  • Member
  • **
  • Posts: 220
    • WJR's website
Re: dinput.h for GoAsm?
« Reply #1 on: January 22, 2014, 04:38:08 PM »
If you uncheck the three items in the xlatHinc Options menu, you will get a straight forward 32-bit Unicode translation (which wouldn't require or use the extra conditional symbols that I use to switch in the other cases). At the first dialog box press Continue, then that is almost it... I see I haven't finished an update for this, so the trailing byte portions of the GUIDs should be within their own nested <>.

satpro

  • Member
  • **
  • Posts: 116
Re: dinput.h for GoAsm?
« Reply #2 on: January 22, 2014, 06:31:36 PM »
That answers it all!  Thank you.  I read the readme over and over, saved the converted dinput8 header file a bunch of different ways, and was sitting here trying to figure out which one to use.  I was at the point of comparing a converted file by hand with other DX files and manually extracting (by best guess) only what I would need to get the job done.  It just so happens one of those converted files is ready to go.  :biggrin:

Thanks again.  I was wondering about the GUIDs and you answered it -- a small matter to fix.

dedndave

  • Member
  • *****
  • Posts: 8827
  • Still using Abacus 2.0
    • DednDave
Re: dinput.h for GoAsm?
« Reply #3 on: January 22, 2014, 09:55:32 PM »
some direct-x GUID's reside in a static lib named dxguid.lib
so, if you want to support some oddball input devices, you may have to add GUID's, or use the library