event module contains traits and structs to actually run your game mainloop
and handle top-level state, as well as handle input events such as keyboard
If you don't want to use
ggez's built in event loop, you can
write your own mainloop and check for events on your own. This is
not particularly hard, there's nothing special about the
EventHandler trait. It just tries to simplify the process a
little. For examples of how to write your own main loop, see the
source code for this module, or the
Provides a way to retrieve events from the system and from the windows that were registered to the events loop.
Gamepad's elements which state can be represented by value from -1.0 to 1.0.
Gamepad's elements which state can be represented by value from 0.0 to 1.0.
Symbolic name for a keyboard key.
Describes a button of a mouse controller.
A trait defining event callbacks. This is your primary interface with
Runs the game's main loop, calling event callbacks on the given state object as events occur.