Switch input system to baton ? #42
Labels
No labels
0. Imported
1. Bug
1. Clean-up
1. Feature
1. Improvement
2. Deliverable
2. Epic
3. Duplicate
3. Invalid
3. Need investigation
4. Assets
4. Birb Core
4. Debug
4. Dependencies
4. Inputs
4. Lang
4. Scenes
4. Screen
4. World
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: epervier/epervier-old#42
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Baton source : https://github.com/tesselode/baton
Making core.inputs a wrapper around Baton could help us simplify a lot the code, by letting Baton doing the heavy lifting, and would give us joystick support at the same time.
Each “player” would be a Baton instance, and core.inputs would be a manager for them all.
( it could also help us simplify the input lock system, by just stopping the bridge between Baton and the scene when inputs are locked. )