REVIEWED: Avoid possible gamepad index as -1
#2839
WARNING: It could require further review of `GamepadThread()` function where `js_event gamepadEvent.number` detecting current pressed button could generate a missmatch with index 0 (reserved for button unknow). Or maybe `0` could just be `GAMEPAD_BUTTON_NONE`? In that case, consistency with other inputs should be carefully considered...
This commit is contained in:
parent
0ccc1d3686
commit
62f63f9e48
2 changed files with 8 additions and 7 deletions
|
@ -716,7 +716,7 @@ typedef enum {
|
|||
|
||||
// Material map index
|
||||
typedef enum {
|
||||
MATERIAL_MAP_ALBEDO = 0, // Albedo material (same as: MATERIAL_MAP_DIFFUSE)
|
||||
MATERIAL_MAP_ALBEDO = 0, // Albedo material (same as: MATERIAL_MAP_DIFFUSE)
|
||||
MATERIAL_MAP_METALNESS, // Metalness material (same as: MATERIAL_MAP_SPECULAR)
|
||||
MATERIAL_MAP_NORMAL, // Normal material
|
||||
MATERIAL_MAP_ROUGHNESS, // Roughness material
|
||||
|
@ -862,7 +862,7 @@ typedef enum {
|
|||
} BlendMode;
|
||||
|
||||
// Gesture
|
||||
// NOTE: It could be used as flags to enable only some gestures
|
||||
// NOTE: Provided as bit-wise flags to enable only desired gestures
|
||||
typedef enum {
|
||||
GESTURE_NONE = 0, // No gesture
|
||||
GESTURE_TAP = 1, // Tap gesture
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue