Difference between revisions of "The Zandalar project"
m (More work on the events) |
m (→Input Aggregator & events) |
||
Line 3: | Line 3: | ||
= Input Aggregator & events = | = Input Aggregator & events = | ||
For start, the following events will cover all existing functions in the 'InjectedInputReceiver' interface: | For start, the following events will cover all existing functions in the 'InjectedInputReceiver' interface: | ||
− | + | ||
− | + | MovementInputEvent | |
− | + | * '''Data''': | |
− | + | ** Position : Vector2 | |
− | + | ** Delta : Vector2 | |
− | + | * '''Functions''': | |
− | + | ** injectMouseMove | |
− | + | ** injectMousePosition | |
− | + | ||
− | + | PressedButtonInputEvent | |
− | + | * '''Data''': | |
− | + | ** Button : Buttons Enum | |
− | + | * '''Functions''': | |
− | + | ** injectMouseButtonDown | |
− | + | ** injectKeyDown | |
− | + | ||
− | + | ReleasedButtonInputEvent | |
− | + | * '''Data''': | |
− | + | ** Button : Buttons Enum | |
− | + | * '''Functions''': | |
− | + | ** injectMouseButtonUp | |
− | + | ** injectKeyUp | |
− | + | ||
− | + | ActivatedInputEvent | |
− | + | * '''Data''': | |
− | + | ** Count (1+) : int | |
− | + | * '''Functions''': | |
− | + | ** injectMouseButtonClick | |
− | + | ** injectMouseButtonDoubleClick | |
− | + | ** injectMouseButtonTripleClick | |
− | + | ||
+ | TextInputEvent | ||
+ | * '''Data''': | ||
+ | ** Text : string/char | ||
+ | * '''Functions''': | ||
+ | ** injectChar | ||
Unmapped (yet) functions: | Unmapped (yet) functions: |
Revision as of 13:07, 24 June 2013
The Zandalar Project is a codename for the new Input archtecture and GUI navigation features.
Input Aggregator & events
For start, the following events will cover all existing functions in the 'InjectedInputReceiver' interface:
MovementInputEvent
- Data:
- Position : Vector2
- Delta : Vector2
- Functions:
- injectMouseMove
- injectMousePosition
PressedButtonInputEvent
- Data:
- Button : Buttons Enum
- Functions:
- injectMouseButtonDown
- injectKeyDown
ReleasedButtonInputEvent
- Data:
- Button : Buttons Enum
- Functions:
- injectMouseButtonUp
- injectKeyUp
ActivatedInputEvent
- Data:
- Count (1+) : int
- Functions:
- injectMouseButtonClick
- injectMouseButtonDoubleClick
- injectMouseButtonTripleClick
TextInputEvent
- Data:
- Text : string/char
- Functions:
- injectChar
Unmapped (yet) functions:
- injectMouseLeaves
- injectMouseWheelChange
Original proposition
Some examples of input events are:
- MovementInputEvent
- Generated from mouse x/y
- Generated from joystick/thumbstick x/y
- PressedInputEvent
- Generated from mouse button
- Generated from keyboard button
- Generated from a gamepad button
One can see that this solution leads us to allow a variety of input to be mapped to certain input events. Of course, each different input event will have some specific payload (the button pressed, the x/y coordinates of the movement, etc.).
At the end of the day, the samples that exist now should work (from the functionality point of view) the same way after the input system is replaced.