search

google-code-export / badquest

Automatically exported from code.google.com/p/badquest
0 stars 0 forks source link

Player must be capable of handling input #39

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
Requires an enumeration of player actions, followed by a mapping of key presses 
to these actions. Consider passing Player the key and click sets. The key here 
is to internalize input to the player. Additionally, this will facilitate the 
ability to lock input within areas of the screen. For example, key presses in 
an overlay state will be easier to cut off from being passed to the Player.

Original issue reported on code.google.com by mikeg3...@gmail.com on 17 Nov 2012 at 3:44

GoogleCodeExporter commented 9 years ago 
Some issues are cropping up surrounding this issue, for example, when collision 
prediction occurs relative to when player input velocity is read.

Original comment by mikeg3...@gmail.com on 17 Nov 2012 at 7:12

GoogleCodeExporter commented 9 years ago 
CollideWithSolids is now called inherently from an object's move method. It has 
been removed from Room's updateAll method.

Original comment by mikeg3...@gmail.com on 17 Nov 2012 at 7:21