Windows平台下使用DirectX（DirectInput8）进行Joystick编程

共2个文件

cpp：1个

pdf：1个

joystick

DirectInput

Windows

Development

1星需积分: 47 174 浏览量 2018-05-28 17:19:24 上传评论 2 收藏 923KB RAR 举报

资源详情

资源评论

资源推荐

收起资源包目录

Windows-Joystick-DirectInput.rar （2个子文件）

Windows-Joystick-DirectInput

Joystick.cpp 24KB

DirectInput8开发手册.pdf 1.18MB

DirectInput

This section provides information about the Microsoft DirectInput component of the

Microsoft DirectX application programming interface (API). The DirectInput API is used

to process data from a joystick, or other game controller. The use of DirectInput for

keyboard and mouse input is not recommended, Windows messages should be used

instead (see Taking Advantage of High-Definition Mouse Movement for additional

information). Note that the XInput API has been introduced for Xbox 360 controller

support on Windows, see XInput and DirectInput for additional information.

Roadmap

Information on using DirectInput is presented in the following sections. Use this page

to guide you through the documentation based on your level of experience as a

DirectInput developer.

Introduction to DirectInput. High-level overview of the capabilities of DirectInput and

the steps you'll take to implement it. Start with this section if you're new to

DirectInput.

Understanding DirectInput. Introduction to the objects and interfaces of DirectInput

and how they are related to the Microsoft Windows message system. Read this section

if you're new to DirectInput.

Using DirectInput. Guide to the API. This section contains more detailed conceptual

information than the previous two sections, as well as information about the API

elements you'll use for setting up devices, retrieving data, and implementing force-

feedback effects. If you're a novice, at least familiarize yourself with the contents of

this section. Later, you can refer to topics as you need them. Use this section in

conjunction with the DirectInput C/C++ Reference.

Programming Tips and Tools. Advanced programming topics and a guide to the

DirectInput tools provided with the DirectX software development kit (SDK).

DirectInput C/C++ Reference. Reference information for the API. Use this section

when you need to know the details of an interface, method, structure, macro, or other

element.

Send feedback to DxSdkDoc@microsoft.com.

Version: 1962.00

Introduction to DirectInput

DirectInput is an API for input devices including the mouse, keyboard, joystick, and

other game controllers, as well as for force-feedback (input/output) devices.

This topic provides a brief overview of the capabilities of DirectInput and how to set it

up in an application. For a more comprehensive view of how DirectInput works, see

Understanding DirectInput. For a step-by-step guide to using the DirectInput API, see

Using DirectInput.

The Power of DirectInput

Page 1 of 143

DirectInput

2018/5/28

file:///C:/Users/HSB-HL/AppData/Local/Temp/~hh5B37.htm

DirectInput enables an application to retrieve data from input devices even when the

application is in the background. It also provides full support for any type of input

device, as well as for force feedback.

Through action mapping, applications can retrieve input data without needing to know

what kind of device is being used to generate it.

The extended services and improved performance of DirectInput make it a valuable

tool for games, simulations, and other real-time interactive applications running under

Windows.

DirectInput does not provide any advantages for applications that use the keyboard

for text entry or the mouse for navigation. For more information, see Interaction with

Windows.

Getting Started with DirectInput

This topic is an overview of what is involved in setting up and using DirectInput in a

simple application.

For details and examples of these steps, see Using DirectInput.

The following steps represent a simple implementation of DirectInput in which the

application takes responsibility for ascertaining what device object (button, axis, and

so on) generated each item of data.

1. Create the DirectInput object.

You use methods of this object to enumerate devices and create DirectInput

device objects.

2. Enumerate devices.

This is not an essential step if you intend to use only the system mouse or

keyboard. To ascertain what other input devices are available on the user's

system, have DirectInput enumerate them. Each time DirectInput finds a device

that matches the criteria you set, it gives you the opportunity to examine the

device's capabilities. It also retrieves a unique identifier that you can use to

create a DirectInput device object representing the device.

3. Create a DirectInputDevice object for each device you want to use.

To do this, you need the unique identifier retrieved during enumeration. For the

system mouse or keyboard, you can use a standard globally unique identifier

(GUID).

4. Set up the device.

Note

To understand DirectInput, it is essential to understand the following terms:

DirectInput object

The root DirectInput interface.

Device

A keyboard, mouse, joystick, or other input device.

DirectInputDevice object

Code representing a keyboard, mouse, joystick, or other input device.

Device object

Code representing a key, button, trigger, and so on found on a DirectInput

device object. Also called device object instance.

Page 2 of 143

DirectInput

2018/5/28

file:///C:/Users/HSB-HL/AppData/Local/Temp/~hh5B37.htm

For each device, first set the cooperative level, which determines the way the

device is shared with other applications or the system. You must also set the

data format used for identifying device objects, such as buttons and axes, within

data packets. If you intend to retrieve buffered data-that is, events rather than

states-you also need to set a buffer size. Optionally, at this stage you can

retrieve information about the device and tailor the application's behavior

accordingly. You can also set properties such as the range of values returned by

joystick axes.

5. Acquire the device.

At this stage you tell DirectInput that you are ready to receive data from the

device.

6. Retrieve data.

At regular intervals, typically on each pass through the message loop or

rendering loop, get either the current state of each device or a record of events

that have taken place since the last retrieval. If you prefer, you can have

DirectInput notify you whenever an event occurs.

7. Act on the data.

The application can respond either to the state of buttons and axes or to events

such as a key being pressed or released.

8. Close DirectInput.

Before exiting, your application should unacquire all devices and release them,

then release the DirectInput object.

This is not the only approach to implementing DirectInput. To take advantage of the

great variety of input devices available now and later, and to simplify configuration for

the user, you can use action mapping.

By setting an action map for a device, you let DirectInput decide which device object

to use for each application action. For example, instead of specifying that the throttle

in your racing game must always be controlled by the y-axis, you can create an action

called AXIS_THROTTLE and have DirectInput assign that action to the most

appropriate axis available on the device. When you retrieve events, you identify them

by their associated actions rather than by the device objects that generated them.

Send feedback to DxSdkDoc@microsoft.com.

Version: 1962.00

Understanding DirectInput

This topic covers the underlying structure of Microsoft DirectInput and its relationship

to the Microsoft Windows message system.

For practical information about how to implement the elements of DirectInput

introduced here, see Using DirectInput.

DirectInput Objects

An input-only DirectInput implementation consists of the DirectInput object, which

Page 3 of 143

DirectInput

2018/5/28

file:///C:/Users/HSB-HL/AppData/Local/Temp/~hh5B37.htm

supports IDirectInput8 Interface, a Component Object Model (COM) interface, and a

DirectInputDevice object for each input device that provides data. Each

DirectInputDevice object in turn has device objects, which are individual controls or

switches, such as keys, buttons, or axes. Device objects are also called device object

instances.

Each DirectInputDevice object represents one input device, such as a mouse,

keyboard, or joystick. In the DirectInput API, the word joystick means any type of

input device other than a mouse or keyboard. A piece of hardware that is really a

combination of different types of input devices, such as a keyboard with a touchpad,

can be represented by two or more DirectInputDevice objects. A force-feedback

device is represented by a single joystick object that handles both input and output.

DirectInputDevice objects instantiate the IDirectInputDevice8 Interface. The

application ascertains the number and type of device objects available by using the

IDirectInputDevice8::EnumObjects method. Individual device objects are not

encapsulated as code objects, but are described in DIDEVICEOBJECTINSTANCE

structures.

All DirectInput interfaces are available in ANSI and Unicode versions. If "UNICODE" is

defined during compilation, the Unicode versions are used.

Interaction with Windows

Because DirectInput works directly with the device drivers, it either suppresses or

ignores Windows mouse and keyboard messages. It also ignores mouse and keyboard

settings made by the user in Control Panel. It does, however, use the calibrations set

for a joystick or other game controller.

DirectInput does not recognize keyboard character repeat settings. When using

buffered data, DirectInput interprets each press and release as a single event with no

repetition. When using immediate data, DirectInput is concerned only with the present

physical state of the keys, not with keyboard events as interpreted by Windows.

DirectInput does not perform any character conversion or translation. For example,

the SHIFT key is treated like any other key, not as a modifier of another keypress.

Keys return the same identifiers regardless of the user's system language settings.

Under Windows 2000, acquiring the keyboard in exclusive mode prevents any

applications that are subsequently launched from receiving keyboard data.

Because DirectInput works directly with the mouse driver, it bypasses the subsystem

of Windows that interprets mouse data for windowed applications. Applications that

rely on the Windows cursor for navigation should continue to use the standard

Windows mouse messages and Microsoft Win32 functions.

When using the system mouse in exclusive mode, DirectInput suppresses mouse

messages, and therefore Windows is unable to show the standard cursor.

DirectInput ignores Control Panel settings such as acceleration and swapped buttons.

However, DirectInput recognizes settings in the driver itself. For example, if the user

has a three-button mouse and uses the driver-utility software to make the middle

button a double-click shortcut, DirectInput reports a click of the middle button as two

clicks of the primary button.

Send feedback to DxSdkDoc@microsoft.com.

Version: 1962.00

Page 4 of 143

DirectInput

2018/5/28

file:///C:/Users/HSB-HL/AppData/Local/Temp/~hh5B37.htm

Using DirectInput

This topic is a guide to implementing Microsoft DirectX. For a broader overview, see

Understanding DirectInput.

This programming guide also provides the following subsections:

l DirectInput Devices

l DirectInput Device Data

l Force Feedback

Creating DirectInput

The first step in any Microsoft DirectInput application is obtaining the IDirectInput8

Interface. You can do this most easily by calling the DirectInput8Create function.

You should create a single DirectInput object and not release it until the application

terminates.

DirectInput Device Enumeration

DirectInput can query the system for all available input devices, determine whether

they are connected, and return information about them. This process is called

enumeration.

If your application is using only the standard keyboard or mouse, or both, you do not

need to enumerate the available input devices. As explained under Creating a

DirectInput Device, you can use predefined global variables when calling the

IDirectInput8::CreateDevice method.

The following code example, where lpdi is a pointer to the IDirectInput8 Interface

interface, creates a keyboard device:

LPDIRECTINPUTDEVICE8 lpdiKeyboard;

lpdi->CreateDevice(GUID_SysKeyboard, &lpdiKeyboard, NULL);

The first parameter in IDirectInput8::CreateDevice is an instance GUID that identifies

the instance of the device for which the interface is to be created. Microsoft

DirectInput has two predefined GUIDs, GUID_SysMouse and GUID_SysKeyboard,

which represent the system mouse and keyboard. You can pass one of these

identifiers into the IDirectInput8::CreateDevice method. The global variable

GUID_Joystick should not be used as a parameter for IDirectInput8::CreateDevice

because it is a product GUID, not an instance GUID.

DirectInput provides four other predefined GUIDs primarily for testing.

l GUID_SysKeyboardEm

l GUID_SysKeyboardEm2

l GUID_SysMouseEm

l GUID_SysMouseEm2

Note

If the computer has more than one mouse, input from all mice is combined to

form the system device. The same is true for multiple keyboards.

Page 5 of 143

DirectInput

2018/5/28

file:///C:/Users/HSB-HL/AppData/Local/Temp/~hh5B37.htm

弗洛伊德VIP

2020-12-08

不能直接使用，源程序应该是个MFC程序，但是只贴了个CPP文件，难搞啊

评论收藏

内容反馈

梦醒浮华

粉丝: 2
资源: 1

Windows平台下使用DirectX（DirectInput8）进行Joystick编程

评论1

最新资源

Windows平台下使用DirectX（DirectInput8）进行Joystick编程

评论1

DIRECTX JOYSTICK 源程序

使用DirectInput来控制游戏代码

Joystick wrapper for DirectInput-开源

利用directinput 进行手柄编程 例程 VC++

Directx Input输入库实现

C#操纵杆(JoyStick)控制例子

C#使用DirectX获取摇杆外设状态

c# DirectX.DirectInput 手柄编程 源代码

microsoft.directx.directinput.dll

directInput_joystick-master_direct_joystick_completelyh2s.zip

DirectInput游戏杆状态获取程序

基于DIRECT X的joystick C++类

C# 基于 directinput 操控手柄

游戏手柄joystick程序

joystick_vb编程

游戏手柄joystick api测试程序

VC++ MFC 游戏手柄Joystick 编程

c# 游戏手柄控制 Joystick

用MFC实现基于DirectInput的键盘消息响应

【C++】DirectInput演示程序demo by浅墨

DirectXInput从入门到精通

多个JoyStick同时测试

pydirectinput:使用直接输入的Windows的Python鼠标和键盘输入自动化

JoystickIn是DirctextX编程中经常用到的关于游戏杆操作的类

c#做的利用Joystick类连接游戏或工业摇杆

C#手柄编程.zip

外接操纵杆的控制代码

最新资源

利用directinput 进行手柄编程例程 VC++

c# DirectX.DirectInput 手柄编程源代码