See: Description
Interface | Description |
---|---|
ButtonListener |
Implement this interface to receive events from a button on the controller.
|
ButtonListenerEDT |
Implement this interface to receive events from a button on the controller.
|
ControllerListener |
Implement this interface to receive events when a controller is connected or
disconnected from your computer.
|
ControllerListenerEDT |
Implement this interface to receive events from a controller.
|
ValueListener |
Implement this interface to receive events from a thumbstick or trigger on the controller.
|
ValueListenerEDT |
Implement this interface to receive events from a thumbstick or trigger on the controller.
|
Class | Description |
---|---|
ControllerButton |
A single button on the Xbox 360 controller.
|
ControllerValue |
A single variable control on the Xbox 360 controller.
|
XInputBatteryInformation |
Contains information on battery type and charge state.
|
XInputCapabilities |
Describes the capabilities of a connected controller.
|
XInputGamepad |
The state of the individual devices on a gamepad.
|
XInputKeystroke |
Specifies keystroke data returned by
J360.XInputGetKeystroke(int, int, com.exlumina.j360.XInputKeystroke) . |
XInputState |
Represents the state of a controller.
|
XInputVibration |
Specifies motor speed levels for the vibration function of a controller.
|
Enum | Description |
---|---|
AccumulationSpeed |
A fixed set of speeds that control how rapidly values change in accumulating mode.
|
Controller |
An individual Xbox 360 controller.
|
DelayInterval |
Defines intervals for buttons in repeat mode that pass before repeating begins.
|
J360 |
Static methods and constants that allow Java-to-Windows access of the XInput API.
|
RepeatInterval |
Defines intervals that pass between repeitions for buttons in repeat mode.
|
Note regarding naming conventions: To match the expectations of C and C++ programmers who
have prior experience with the Windows XInput API, J360Controller methods and variables
that correspond directly to Windows API functions and variables use the same names as their
Windows counterparts. Windows API calls are not consistent about capitalization, which
means that some Windows functions start with an upper-case letter and some start with a
lower-case letter (as opposed to the standard convention in Java programs, which calls for
all methods that are not constructors to start with a lower-case letter). In particular,
all of the J360Controller methods in the J360
class that mimic
XInput functions start with the capital letters, "XI," just as they do in the actual
Windows API declarations.