Open main menu
Home
Random
Recent changes
Special pages
Community portal
Preferences
About Wikipedia
Disclaimers
Incubator escapee wiki
Search
User menu
Talk
Dark mode
Contributions
Create account
Log in
Editing
DirectInput
(section)
Warning:
You are not logged in. Your IP address will be publicly visible if you make any edits. If you
log in
or
create an account
, your edits will be attributed to your username, along with other benefits.
Anti-spam check. Do
not
fill this in!
{{short description|Microsoft API}} {{Redirect|XInput|the X Window System XInput extension|X Window System protocols and architecture}} In computing, '''DirectInput''' is a legacy<ref>{{Cite web|url=https://docs.microsoft.com/previous-versions/windows/desktop/ee416842(v=vs.85)|title=DirectInput|date=10 September 2011 }}</ref> [[Microsoft]] [[API]] for collecting input from a computer user, via [[list of input devices|input devices]] such as the [[computer mouse|mouse]], [[computer keyboard|keyboard]], or a [[gamepad]]. It also provides a system for ''action mapping,'' which allows the user to assign specific actions within a game to the buttons and axes of the input devices. Additionally it handles ''[[haptic technology#Video games|haptic feedback]]'' (input/output) devices. Microsoft introduced a new input library called XInput specifically for the [[Xbox 360 controller]]. DirectInput and XInput provide benefits over normal Win32 input events: * they enable an application to retrieve data from input devices even when the application is in the background * they provide full support for any type of input device, as well as for ''haptic feedback'' * through ''action mapping'', applications can retrieve input data without needing to know what kind of device generated that input While DirectInput forms a part of the [[DirectX]] library, it has not been significantly revised since DirectX 8 (2001β2002). Microsoft recommends that new applications make use of the [[Message loop in Microsoft Windows|Windows message loop]] for keyboard and mouse input instead of DirectInput (as indicated in the Meltdown 2005 slideshow<ref>{{cite web |url=http://download.microsoft.com/download/b/0/0/b0095d07-01fe-47f1-ad3c-fc463f88ef83/Meltdown2005.zip |title=Meltdown 2005 slideshow (.zip) |access-date=2012-11-13 |url-status=bot: unknown |archive-url=https://web.archive.org/web/20150521162503/http://download.microsoft.com/download/b/0/0/b0095d07-01fe-47f1-ad3c-fc463f88ef83/Meltdown2005.zip |archive-date=2015-05-21 }}</ref>), and to use GameInput instead of DirectInput and other legacy APIs, such as XInput, for controllers.<ref>{{cite web |title=Overview of GameInput |date=28 March 2024 |url=https://learn.microsoft.com/en-us/gaming/gdk/_content/gc/input/overviews/input-overview |page=GameInput introduction, "Getting started" |quote=GameInput is the recommended API for all new code, regardless of the target platform, because it provides support across all Microsoft platforms (including earlier versions of Windows), and provides superior performance versus legacy APIs.}}</ref>
Edit summary
(Briefly describe your changes)
By publishing changes, you agree to the
Terms of Use
, and you irrevocably agree to release your contribution under the
CC BY-SA 4.0 License
and the
GFDL
. You agree that a hyperlink or URL is sufficient attribution under the Creative Commons license.
Cancel
Editing help
(opens in new window)