Windows.Gaming.Input.Custom Namespace

Contains APIs enabling equipment manufacturers to write custom WinRT (Windows Runtime) class libraries for their devices.

Classes

GameControllerFactoryManager

Manages factories for custom controllers.

GipFirmwareUpdateResult

The result of an update operation.

GipGameControllerProvider

Represents a physical game controller connected to the system using GIP.SYS (for Xbox One accesories).

HidGameControllerProvider

Represents the underlying device for a HID (Human Interface Device) game controller.

XusbGameControllerProvider

Represents the physical game controller devices connected to the system using XUSB22.SYS (for Xbox 360 accessories).

Structs

GameControllerVersionInfo

Contains information on the game controller version.

GipFirmwareUpdateProgress

Indicates the progress of a firmware update operation.

Interfaces

ICustomGameControllerFactory

Represents a factory for creating a custom controller type.

IGameControllerInputSink

Base interface that defines the interfaces necessary to write a custom game controller class.

IGameControllerProvider

Base interface that represents the physical game controller devices connected to the system.

IGipGameControllerInputSink

Defines the methods necessary for a custom Gip controller interface.

IHidGameControllerInputSink

Defines the methods necessary for a custom HID (Human Interface Device) controller interface.

IXusbGameControllerInputSink

Defines the methods necessary for a custom Xusb controller interface.

Enums

GipFirmwareUpdateStatus

Indicates the state of a firmware update operation.

GipMessageClass

The class of a Gip message.

XusbDeviceSubtype

The device subtype of the controller.

XusbDeviceType

The device type of the controller.

Remarks

It is important to be aware that the APIs in this namespace are not targeted at apps; in fact, no app should ever call these APIs directly. This namespace is only meant to provide a framework for authoring WinRT component libraries, and it is those libraries (and the APIs they expose) that apps will ultimately consume. As such, these APIs are focused primarily on low-level, raw access to game controller devices.