Warning: This site is under construction, most links will be broken.

LightX API -> lxinputjoypad -> caps [fields]

Last modified on Wed, 9th May 2007 at 14:43 UTC by zipplet

caps_name: string;
caps_buttons: integer;
caps_has_z: boolean;
caps_has_r: boolean;
caps_has_u: boolean;
caps_has_v: boolean;
caps_has_dpad: boolean;
caps_has_rumble: boolean;
caps_padtype: tlxpadtype;


These fields return information about the capabilities of a controller. They are populated either after a call to lxinputjoypad.getcaps or lxinputjoypad.setpad. Use these fields to determine what axes are available, the controllers name, number of buttons, etc.

Note: The X and Y axes are always available.

It is impossible to determine the physical layout of a controller, except for if the controller is an xbox 360 controller and the descendant used is the xinput class (then the layout is known, and fixed).

caps_name will return a friendly name for the controller. Currently, it is not possible for the mmsystem or xinput descendants to assign a meaningful friendly name. This is not so important with the xinput descendant, but it is a reasonably serious issue with other gamepads.

The type of controller (caps_padtype) will usually be padGeneric. See tlxpadtype definition.

Class: lxinputjoypad