File: input.txt

package info (click to toggle)
fuse-emulator 1.1.1%2Bdfsg1-2
  • links: PTS
  • area: main
  • in suites: jessie, jessie-kfreebsd
  • size: 11,120 kB
  • ctags: 8,968
  • sloc: ansic: 78,960; sh: 11,228; perl: 3,742; makefile: 1,104; yacc: 236; lex: 140
file content (93 lines) | stat: -rw-r--r-- 2,325 bytes parent folder | download | duplicates (5)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
As of version 0.7.0, Fuse has a generalised 'input layer' designed to
abstract out the vagaries of how each user interface handles user
input and to help ensure consistency between the various user
interfaces.

When some input is received from the user, the user interface code
should set up an input_event_t structure and then simply call
input_event().

input_event_t is defined as follows:

typedef struct input_event_t {

  input_event_type type;

  union {

    input_event_key_t key;
    input_event_joystick_t joystick;

  } types;

} input_event_t;

The 'type' member specifies what sort of input has occurred. The
following event types are supported:

* Key events

  These receive event-specific data in 'types.key', which is defined
  as

typedef struct input_event_key_t {

  input_key key;

} input_event_key_t;

  The 'input_key' type is defined in input.h and specifies which key
  this event refers to.

  Event types:

  * INPUT_EVENT_KEYPRESS
    The key specified in types.key.key has been pressed.

  * INPUT_EVENT_KEYRELEASE
    The key specified in types.key.key has been released.

* Joystick events

  These receive event-specific dat in 'types.joystick', which is
  defined as

typedef struct input_event_joystick_t {

  int which;
  input_joystick_button button;

} input_event_joystick_t;

  'which' specifies the joystick which produced this event. which == 0
  refers to the joystick Fuse thinks of as 'Joystick 1' while which ==
  1 refers to 'Joystick 2'. 'button' refers to the state of the
  joystick, and can take one of the following values:

  * INPUT_JOYSTICK_UP
  * INPUT_JOYSTICK_DOWN
  * INPUT_JOYSTICK_LEFT
  * INPUT_JOYSTICK_RIGHT
  * INPUT_JOYSTICK_FIRE_1
  * INPUT_JOYSTICK_FIRE_2
  * INPUT_JOYSTICK_FIRE_3
  * INPUT_JOYSTICK_FIRE_4
  * INPUT_JOYSTICK_FIRE_5
  * INPUT_JOYSTICK_FIRE_6
  * INPUT_JOYSTICK_FIRE_7
  * INPUT_JOYSTICK_FIRE_8
  * INPUT_JOYSTICK_FIRE_9
  * INPUT_JOYSTICK_FIRE_10

  The INPUT_JOYSTICK_FIRE_<n> constants are guaranteed to have
  consecutive values.

  Event types:

  * INPUT_EVENT_JOYSTICK_PRESS
    The joystick specified in types.joystick.which has entered the
    state specified in types.joystick.button.

  * INPUT_EVENT_JOYSTICK_RELEASE
    The joystick specified in types.joystick.which has left the state
    specified in types.joystick.button.