We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
To be handled at the application level, but interpreted at the game engine level.
The game engine would then be able to interpret these messages/events in order to produce its own device-agnostic input events, etc.
The text was updated successfully, but these errors were encountered:
Added tag for app module. May change this to its own standalone module (rather than a submodule of app) at a later date.
app
Sorry, something went wrong.
No branches or pull requests
To be handled at the application level, but interpreted at the game engine level.
Input devices include:
Each device type should have its own event types that relay appropriate state information, split into two categories:
The game engine would then be able to interpret these messages/events in order to produce its own device-agnostic input events, etc.
Other features:
The text was updated successfully, but these errors were encountered: