Closed cvan closed 9 years ago
Or maybe FrameManager
has been superseded by these other components. It's a bit hard to tell. @KevinGrandon?
Yup, the idea here is that we want to move everything into browser.js or other components.
Frame manager just remains in the code base so it's clear what's left to migrate. Sorry for not being more clear there.
Oh, shoot, okay. There's a lot of code in there to migrate.
Oh, shoot, okay. There's a lot of code in there to migrate.
There's a fair amount yeah, but it should go pretty quickly. I recommend handling it piece by piece to fix the issues listed in your original comment. I'll be around to help out :)
okay, no problemo. I'll close this issue. as long as @caseyyee too knows where to look. thanks!
Yup, already working on these :)
FrameManager
is no longer getting initalised inbrowser.js
, and as such theFrameManager#init
method isn't called, so none of the mouse events, keyboard inputs, and gamepad inputs are getting set up.Looks like it's probably the culprit to #216, #217, #219, #220. It probably won't immediately fix all those issues, but it looks like a start.