Home > Articles

  • Print
  • + Share This
This chapter is from the book

The T3DLIB2 DirectX Input System

Writing a simple set of wrapper functions around DirectInput is almost a no-brainer. Well, it takes some brains, but for the most part it's fairly easy. All we need to do is create an API with a very simple interface and few parameters. The interface should support the following minimal functionality:

  • Initialize the DirectInput system

  • Set up and acquire the keyboard, mouse, and joystick—or any subset

  • Read data from any of the input devices

  • Shut down, unacquire, and release everything

I have created such an API, and it's available in T3DLIB2.CPP|H on the CD. The API does everything you need to initialize DirectInput and read any device. Before reviewing the functions, take a look at Figure 3.11—it depicts the relationship between each device and the data flow.

Figure 3.11Figure 3.11 The DirectInput software system.

Here are the globals for the library:

LPDIRECTINPUT8  lpdi;  // dinput object
LPDIRECTINPUTDEVICE8 lpdikey; // dinput keyboard
LPDIRECTINPUTDEVICE8 lpdimouse; // dinput mouse
LPDIRECTINPUTDEVICE8 lpdijoy; // dinput joystick
GUID joystickGUID; // guid for main joystick
char joyname[80]; // name of joystick

// all input is stored in these records
UCHAR keyboard_state[256]; // contains keyboard state table
DIMOUSESTATE mouse_state; // contains state of mouse
DIJOYSTATE joy_state;  // contains state of joystick
int joystick_found;  // tracks if stick is plugged in

Input from the keyboard is placed in keyboard_state[], the mouse data is stored in mouse_state, and the joystick data is stored in joy_state by the input system. The structure of each of these records is the standard DirectInput device state structures (except for the keyboard; it's just a Boolean array of BYTES) as shown in the following:

// for the mouse data
typedef struct DIMOUSESTATE {
 LONG lX; // x-axis
 LONG lY; // y-axis
 LONG lZ; // z-axis
 BYTE rgbButtons[4]; // state of the buttons
} DIMOUSESTATE, *LPDIMOUSESTATE;

// for the joystick data
typedef struct DIJOYSTATE {
 LONG lX; // x-axis
 LONG lY; // y-axis
 LONG lZ; // z-axis
 LONG lRx; // rotation about x-axis
 LONG lRy; // rotation about y-axis
 LONG lRz; // rotation about z-axis
 LONG rglSlider[2]; // u,v slider positions
 DWORD rgdwPOV[4]; // point of view hat state
 BYTE rgbButtons[32]; // state of buttons 0..31
} DIJOYSTATE, *LPDIJOYSTATE;

In general, the mouse and joystick are roughly equivalent as far as the x,y position goes; that is, you access them via the fields lX, lY, and the buttons are BOOLEANs in rgbButtons[]. Let's get to the functions. The variable joystick_found is a BOOLEAN that is set when you request joystick access. If a joystick is found, it is TRUE, otherwise, it's FALSE. With it, you can conditional block out code that uses the joystick. So without further ado, here is the new API:

Function Prototype:

int DInput_Init(void);

Purpose:

DInput_Init() initializes the DirectInput input system. It creates the main COM object and returns TRUE if successful and FALSE otherwise. And of course, the global lpdi will be valid. The function does not create any devices, though. Here's an example of initializing the input system:

Example:

if (!DInput_Init())
 { /* error */ }

Function Prototype:

void DInput_Shutdown(void);

Purpose:

DInput_Shutdown() releases all the COM objects and any resources allocated during the call to DInput_Init(). Normally, you would call DInput_Shutdown() at the very end of your application after you have released all the input devices themselves—which we'll get to shortly. Anyway, here's an example of shutting down the input system:

Example:

DInput_Shutdown();

Function Prototype:

DInput_Init_Keyboard(void);

Purpose:

DInput_Init_Keyboard() initializes and acquires the keyboard. This should always work and return TRUE, unless another DirectX application has taken over in a really uncooperative way. Here's an example:

Example:

if (!DInput_Init_Keyboard())
 { /* error */ }

Function Prototype:

int DInput_Init_Mouse(void);

Purpose:

DInput_Init_Mouse() initializes and acquires the mouse. The function takes no parameters and returns TRUE if successful and FALSE otherwise. But it should always work, unless a mouse isn't plugged in or there's another DirectX application that has totally taken over! If everything goes well, lpdimouse becomes the valid interface pointer. Here's an example:

Example:

if (!DInput_Init_Mouse()) { /* error */ }

Function Prototype:

int DInput_Init_Joystick(int min_x=-256, // min x range
    int max_x=256, // max x range
    int min_y=-256, // min y range
    int max_y=256, // max y range
    int dead_zone=10); // dead zone in percent

Purpose:

DInput_Init_Joystick() initializes the joystick device for use. The function takes five parameters that define the x-y range of motion of the data sent back from the joystick and the dead zone with a percentage. If you want to use the defaults of -256 to 256 and 10% dead zone for each axis, you don't need to send parameters because they have default values (C++ thing). If the call returns back a TRUE, a joystick was found and it has been set up, initialized, and acquired. After the call, the interface pointer lpdijoy will be valid if you need it for anything. In addition, the string joyname[] will contain the "friendly" name of the joystick device, such as "Microsoft Sidewinder Pro," and so on.

Here's an example of initializing the joystick and setting its x-y ranges to -1024 to 1024 with a 5% dead zone:

Example:

if (!DInput_Init_Joystick(-1024, 1024, -1024, 1024, 5))
 { /* error */ }

Function Prototype(s):

void DInput_Release_Joystick(void);
void DInput_Release_Mouse(void);
void DInput_Release_Keyboard(void);

Purpose:

DInput_Release_Joystick(), DInput_Release_Mouse(), and DInput_Release_Keyboard() release each of the respective input devices when you are done with them. The functions can be called even if you haven't initialized the respective device, so you can just call them all at the end of your application if you want. Here's a complete example of starting up the DirectInput system, initializing all the devices and then releasing them and shutting down:

Example:

// initialize the DirectInput system
DInput_Init();

// initialize all input devices and acquire them
DInput_Init_Joystick();
DInput_Init_Mouse();
DInput_Init_Keyboard();

// input loop ....do work here
// now done...

// first release all devices, order is unimportant
DInput_Release_Joystick();
DInput_Release_Mouse();
DInput_Release_Keyboard();

// shutdown DirectInput
DInput_Shutdown();

Function Prototype:

int DInput_Read_Keyboard(void);

Purpose:

DInput_Read_Keyboard() scans the keyboard state and places the data in keyboard_state[], which is an array of 256 BYTEs. This is the standard DirectInput keyboard state array, so you must use the DirectInput key constants DIK_* if you want to make sense of it. If a key is pressed, the array value will be 0x80. Here's an example of testing whether the right and left keys are down using the manifest constants in DirectInput—which you can look up in the SDK or the abridged Table 3.2 following.

Example:

// read the keyboard
if (!DInput_Read_Keyboard())
 { /* error */ }

// now test the state data
if (keyboard_state[DIK_RIGHT])
 { /* move ship right */ }
else
if (keyboard_state[DIK_LEFT])
 { /* move ship left */ }

Table 3.2 The DirectInput Keyboard State Constants

Symbol

Meaning

DIK_ESCAPE

The Esc key

DIK_0-9

Main keyboard 0–9

DIK_MINUS

Minus key

DIK_EQUALS

Equals key

DIK_BACK

Backspace key

DIK_TAB

Tab key

DIK_A-Z

Letters A–Z

DIK_LBRACKET

Left bracket

DIK_RBRACKET

Right bracket

DIK_RETURN

Return/Enter on main keyboard

DIK_LCONTROL

Left control

DIK_LSHIFT

Left shift

DIK_RSHIFT

Right shift

DIK_LMENU

Left Alt

DIK_SPACE

Spacebar

DIK_F1-15

Function keys 1–15

DIK_NUMPAD0-9

Numeric keypad keys 0–9

DIK_ADD

+ on numeric keypad

DIK_NUMPADENTER

Enter on numeric keypad

DIK_RCONTROL

Right control

DIK_RMENU

Right Alt

DIK_HOME

Home on arrow keypad

DIK_UP

UpArrow on arrow keypad

DIK_PRIOR

PgUp on arrow keypad

DIK_LEFT

LeftArrow on arrow keypad

DIK_RIGHT

RightArrow on arrow keypad

DIK_END

End on arrow keypad

DIK_DOWN

DownArrow on arrow keypad

DIK_NEXT

PgDn on arrow keypad

DIK_INSERT

Insert on arrow keypad

DIK_DELETE

Delete on arrow keypad


(Note: bolded entries simply mean to follow the sequence. For example, DIK_0-9 means that there are constants DIK_0, DIK_1, DIK_2, and so forth.)

Function Prototype:

int DInput_Read_Mouse(void);

Purpose:

DInput_Read_Mouse() reads the relative mouse state and stores the result in mouse_state, which is a DIMOUSESTATE structure. The data is in relative delta mode. In most cases, you'll only need to look at mouse_state.lX, mouse_state.lY, and rgbButtons[0..2], which are BOOLEANs for the three mouse buttons. Here's an example of reading the mouse and using it to move a cursor around and draw:

Example:

// read the mouse
if (!DInput_Read_Mouse())
 { /* error */ }

// move cursor
cx+=mouse_state.lX;
cy+=mouse_state.lY;

// test if left button is down
if (mouse_state.rgbButtons[0])
 Draw_Pixel(cx,cy,col,buffer,pitch);

Function Prototype:

int DInput_Read_Joystick(void);

Purpose:

DInput_Read_Joystick() polls the joystick and then reads the data into joy_state, which is a DIJOYSTATE structure. Of course, if there isn't a joystick plugged in, the function returns FALSE and joy_state will be invalid, but you get the idea. If successful, joy_state contains the state information of the joystick. The data returned will be in the range you previously set for each axis, and the button values are BOOLEANs in rgbButtons[]. As an example, here's how you would use the joystick to move a ship right and left and the first button to fire:

Example:

// read the joystick data
if (!DInput_Read_Joystick())
 { /* error */ }

// move the ship
ship_x+=joy_state.lX;
ship_y+=joy_state.lY;

// test for trigger
if (joy_state.rgbButtons[0])
 { // fire weapon // }

Of course, your joystick might have a lot of buttons and multiple axes. In this case, you can use the other fields of joy_state as defined in the DIJOYSTATE DirectInput structure.

NOTE

Even though we are using the IDIRECTINPUTDEVICE8 interface, we don't need to use the DIJOYSTATE2 structure. This is only for force feedback devices.

At this point, we are ready to take a look at one of the subsystems that most game programmers hate to deal with—sound and music! But under DirectX, along with my wrapper functions, making sound effects and playing music is so easy it's actually fun!

  • + Share This
  • 🔖 Save To Your Account

InformIT Promotional Mailings & Special Offers

I would like to receive exclusive offers and hear about products from InformIT and its family of brands. I can unsubscribe at any time.

Overview


Pearson Education, Inc., 221 River Street, Hoboken, New Jersey 07030, (Pearson) presents this site to provide information about products and services that can be purchased through this site.

This privacy notice provides an overview of our commitment to privacy and describes how we collect, protect, use and share personal information collected through this site. Please note that other Pearson websites and online products and services have their own separate privacy policies.

Collection and Use of Information


To conduct business and deliver products and services, Pearson collects and uses personal information in several ways in connection with this site, including:

Questions and Inquiries

For inquiries and questions, we collect the inquiry or question, together with name, contact details (email address, phone number and mailing address) and any other additional information voluntarily submitted to us through a Contact Us form or an email. We use this information to address the inquiry and respond to the question.

Online Store

For orders and purchases placed through our online store on this site, we collect order details, name, institution name and address (if applicable), email address, phone number, shipping and billing addresses, credit/debit card information, shipping options and any instructions. We use this information to complete transactions, fulfill orders, communicate with individuals placing orders or visiting the online store, and for related purposes.

Surveys

Pearson may offer opportunities to provide feedback or participate in surveys, including surveys evaluating Pearson products, services or sites. Participation is voluntary. Pearson collects information requested in the survey questions and uses the information to evaluate, support, maintain and improve products, services or sites, develop new products and services, conduct educational research and for other purposes specified in the survey.

Contests and Drawings

Occasionally, we may sponsor a contest or drawing. Participation is optional. Pearson collects name, contact information and other information specified on the entry form for the contest or drawing to conduct the contest or drawing. Pearson may collect additional personal information from the winners of a contest or drawing in order to award the prize and for tax reporting purposes, as required by law.

Newsletters

If you have elected to receive email newsletters or promotional mailings and special offers but want to unsubscribe, simply email information@informit.com.

Service Announcements

On rare occasions it is necessary to send out a strictly service related announcement. For instance, if our service is temporarily suspended for maintenance we might send users an email. Generally, users may not opt-out of these communications, though they can deactivate their account information. However, these communications are not promotional in nature.

Customer Service

We communicate with users on a regular basis to provide requested services and in regard to issues relating to their account we reply via email or phone in accordance with the users' wishes when a user submits their information through our Contact Us form.

Other Collection and Use of Information


Application and System Logs

Pearson automatically collects log data to help ensure the delivery, availability and security of this site. Log data may include technical information about how a user or visitor connected to this site, such as browser type, type of computer/device, operating system, internet service provider and IP address. We use this information for support purposes and to monitor the health of the site, identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents and appropriately scale computing resources.

Web Analytics

Pearson may use third party web trend analytical services, including Google Analytics, to collect visitor information, such as IP addresses, browser types, referring pages, pages visited and time spent on a particular site. While these analytical services collect and report information on an anonymous basis, they may use cookies to gather web trend information. The information gathered may enable Pearson (but not the third party web trend services) to link information with application and system log data. Pearson uses this information for system administration and to identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents, appropriately scale computing resources and otherwise support and deliver this site and its services.

Cookies and Related Technologies

This site uses cookies and similar technologies to personalize content, measure traffic patterns, control security, track use and access of information on this site, and provide interest-based messages and advertising. Users can manage and block the use of cookies through their browser. Disabling or blocking certain cookies may limit the functionality of this site.

Do Not Track

This site currently does not respond to Do Not Track signals.

Security


Pearson uses appropriate physical, administrative and technical security measures to protect personal information from unauthorized access, use and disclosure.

Children


This site is not directed to children under the age of 13.

Marketing


Pearson may send or direct marketing communications to users, provided that

  • Pearson will not use personal information collected or processed as a K-12 school service provider for the purpose of directed or targeted advertising.
  • Such marketing is consistent with applicable law and Pearson's legal obligations.
  • Pearson will not knowingly direct or send marketing communications to an individual who has expressed a preference not to receive marketing.
  • Where required by applicable law, express or implied consent to marketing exists and has not been withdrawn.

Pearson may provide personal information to a third party service provider on a restricted basis to provide marketing solely on behalf of Pearson or an affiliate or customer for whom Pearson is a service provider. Marketing preferences may be changed at any time.

Correcting/Updating Personal Information


If a user's personally identifiable information changes (such as your postal address or email address), we provide a way to correct or update that user's personal data provided to us. This can be done on the Account page. If a user no longer desires our service and desires to delete his or her account, please contact us at customer-service@informit.com and we will process the deletion of a user's account.

Choice/Opt-out


Users can always make an informed choice as to whether they should proceed with certain services offered by InformIT. If you choose to remove yourself from our mailing list(s) simply visit the following page and uncheck any communication you no longer want to receive: www.informit.com/u.aspx.

Sale of Personal Information


Pearson does not rent or sell personal information in exchange for any payment of money.

While Pearson does not sell personal information, as defined in Nevada law, Nevada residents may email a request for no sale of their personal information to NevadaDesignatedRequest@pearson.com.

Supplemental Privacy Statement for California Residents


California residents should read our Supplemental privacy statement for California residents in conjunction with this Privacy Notice. The Supplemental privacy statement for California residents explains Pearson's commitment to comply with California law and applies to personal information of California residents collected in connection with this site and the Services.

Sharing and Disclosure


Pearson may disclose personal information, as follows:

  • As required by law.
  • With the consent of the individual (or their parent, if the individual is a minor)
  • In response to a subpoena, court order or legal process, to the extent permitted or required by law
  • To protect the security and safety of individuals, data, assets and systems, consistent with applicable law
  • In connection the sale, joint venture or other transfer of some or all of its company or assets, subject to the provisions of this Privacy Notice
  • To investigate or address actual or suspected fraud or other illegal activities
  • To exercise its legal rights, including enforcement of the Terms of Use for this site or another contract
  • To affiliated Pearson companies and other companies and organizations who perform work for Pearson and are obligated to protect the privacy of personal information consistent with this Privacy Notice
  • To a school, organization, company or government agency, where Pearson collects or processes the personal information in a school setting or on behalf of such organization, company or government agency.

Links


This web site contains links to other sites. Please be aware that we are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of each and every web site that collects Personal Information. This privacy statement applies solely to information collected by this web site.

Requests and Contact


Please contact us about this Privacy Notice or if you have any requests or questions relating to the privacy of your personal information.

Changes to this Privacy Notice


We may revise this Privacy Notice through an updated posting. We will identify the effective date of the revision in the posting. Often, updates are made to provide greater clarity or to comply with changes in regulatory requirements. If the updates involve material changes to the collection, protection, use or disclosure of Personal Information, Pearson will provide notice of the change through a conspicuous notice on this site or other appropriate way. Continued use of the site after the effective date of a posted revision evidences acceptance. Please contact us if you have questions or concerns about the Privacy Notice or any objection to any revisions.

Last Update: November 17, 2020