Hi,
after making some major changes, my keys stopped working properly. Since I thought I might as well update the engine, I downloaded the latest version (the one with GTK3).
I’ve been trying to find the bug all day.
It turned out that the new engine behaves differently.
The keys container.Pressed.keys[keyW] (WASD) are no longer triggered, as if I’m not pressing any keys at all.
But for example, shift-W still works, as does the ESCAPE key.
Of course, it could also be related to the structure of my entire app. I just wanted to ask if others are also experiencing problems.
Thank you very much.
1 Like
Fixed, thank you for reporting!
Indeed I broke it when upgrading GTK 2 → 3, the state of “being pressed” for keyA .. keyZ (as well as KeyDown / KeyUp with Key values between keyA .. keyZ) was not correctly passed.
Fixed in this commit (in GitHub master branch already): Fix generating KeyDown / KeyUp events with keys between keyA ... keyZ… · castle-engine/castle-engine@287bff9 · GitHub . As usual, the fix will be available in the official engine downloads in a few hours, once it passes a few automatic tests. You can watch this page, when it will no longer contain the commit titled "Fix generating KeyDown / KeyUp events with keys between keyA … keyZ" → then the fix is included in the downloads and you can just upgrade the engine to have it fixed.
Regards!