You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
To better future-proof the project, we should hide as much of GLFW as possible from anything other than the main engine class.
As it is, most input is handled there, mapped into the ActionState class, but we use our own state enumerations like FORWARD, BACK, LEFT.
In commit c93e2ca we hid the mouse input modes using the engine class, let's continue doing things like that until glfw isn't used anywhere else but directly in the engine class.
The text was updated successfully, but these errors were encountered:
- Solved most of issue #42.
- remaining glfw usages rely on keyboard enumerations. These will be later replaced when we implement issue #43 and create a keyboard event (like a mouse event)
- Fixed bug where pause menu wouldn't reopen when closed using the "resume" button.
Issue mostly solved in commit e906a12, though the remainder will be resolved when issue #43 is resolved.
Closing for now, unless some unforeseeable issue re-arises.
To better future-proof the project, we should hide as much of GLFW as possible from anything other than the main engine class.
As it is, most input is handled there, mapped into the ActionState class, but we use our own state enumerations like FORWARD, BACK, LEFT.
In commit c93e2ca we hid the mouse input modes using the engine class, let's continue doing things like that until glfw isn't used anywhere else but directly in the engine class.
The text was updated successfully, but these errors were encountered: