keydown | client side module for firing events | Keyboard library

CSS Classes are case sensitive. e.code returns the String in the format of "Key{key}', and since your class name isn't capitalized, it isn't selected.

Change the class name so have a capital K (e.g, "KeyA").

Collision detection depends on your needs.

• Bounding boxes are simple and can detect if the x, y edges of each object are not within one another. This is fine for fast moving games and things where you don't necessarily require point precision.
• Distance vectors are also simple and perfect solution for circle collisions. They calculate the difference in distance between two objects according to a radius prescribed with the hypotenuse of distX^2 + distY^2.
• Compound bounding objects are harder to calculate, especially for concave areas on objects of arbitrary shape. There are too many notable and novel approaches to collision detection beyond these to remark on here.

They're also increasingly complex depending on things like variability (if they're deformable objects, if they have particle seams, etc and 2d vs 3d object collision can be vastly different worlds as well. There are tons of articles, but I'll post one with implementation here

Here's an example you can follow. First you store the phrase as an array, and for every keydown, compare the event.key with the letter that matches the counter index of the phrase array. For each correctly keyed letter, you advance your counter. Look through this code to get an idea of how it works

this in your code is not what you expect it to be. If block1 etc are local variables, reference them without this.. If they are members of your encapsulating object, change your callback function to use arrow syntax to let this reference your object: document.addEventListener('keydown', event => { /*...*/ })

With JavaScript you can insert a space (' ') when you detect the contenteditable is empty. This pushes the caret position to the center.

Use pygame.time.Clock to control the frames per second and thus the game speed.

The method tick() of a pygame.time.Clock object, delays the game in that way, that every iteration of the loop consumes the same period of time. See pygame.time.Clock.tick():

This method should be called once per frame.

e.g.:

First of all, you should not update the coordinates of the crates from the movement of the camera. Instead, let the camera have its own position in 3D space, update that position when you want the player to move, and then subtract the camera position from the crates' positions when calculating the 2D space coordinates. This will make things much easier when you later want to add, for example, the ability for the camera to rotate or the crates themselves to move.

Now to add a rotation capability to the camera, you will need to define a rotation matrix for it in addition to a position. Then, when rendering the crates, you transform the crate coordinates (after subtracting the camera's position) using the inverse of the camera's rotation matrix. This will give you the view space coordinates of the crates, which should be projected onto the 2D space for rendering.

There are many ways to create a rotation matrix depending on what parameters you have. A common one is the Rodrigues rotation formula or "axis-angle" formula, which is used when you have an axis of rotation and an angle to rotate about that axis. Another one is from Euler angles. And if you aren't familiar with matrices and linear algebra, I would recommend you to learn it (there are a lot of free resources available online) as it is used extensively in 3D game development.

As mentioned by @Mike 'Pomax' Kamermans in the comments, every time you say () => aFunction(), you're creating a completely new function. Just pass in the raw function like aFunction.

It also appears that you're not passing the event variable correctly, I've fixed that too in the codeblock below.

Try this :

1- Give your datagrid a name (use x:name)

2- put this in your constructor :