Content deleted Content added
No edit summary |
m Task 16: replaced (2×) / removed (0×) deprecated |dead-url= and |deadurl= with |url-status=; |
||
Line 9:
* 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)
== History ==
Line 15:
While Microsoft initially intended that DirectInput would handle all inputs, it hasn't turned out this way. {{As of | 2011}} Microsoft doesn't recommend using DirectInput for keyboards or mice, and has started pushing the newer XInput for Xbox 360 controllers.<ref>{{cite web|url=https://msdn.microsoft.com/en-us/library/ee418864.aspx |title=Taking Advantage of High-Definition Mouse Movement |work=MSDN |publisher=Microsoft |accessdate=2009-01-25}}
</ref> In [[Windows Vista]], [[Windows 7]] and later Windows versions, the in-built action mapping UI has been removed.<ref>{{cite web|url=http://forums.microsoft.com/msdn/showpost.aspx?postid=1198467&siteid=1 |title=DirectInput ConfigureDevices in Windows Vista |publisher=Web.archive.org |date=2008-12-27 |accessdate=2012-11-13 |
== XInput ==
| |||