-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Playground: Incorrect focus logic #146
Comments
When we were having issues with SAVESCUM de-focusing I applied quick fix so that every time you resize and click the window, it will focus on the canvas. If you use the shell.html from tophat - that is the reason. |
@skejeton Do you mean we need to implement switching the input focus between the text area and the example window? Are you sure this is possible with the official Sokol? Great if it is. But your SaveScum build was using a customized Sokol fork. |
I did some changes to the playground and I can now finally recreate your issue. |
I found the issue: the newly added event bubble up options were not enabled by tophat. I fixed this in the recent commit. Now it is possible to use the text box. However the issue with both the text box and the game catching the inputs is still there. This issue will require some more work. |
Signed-off-by: Marek Maškarinec <marek@mrms.cz>
The new playground is now uploaded to the website. |
I tested the moving rectangle example with the latest version. The only problem is that the WASD keys, when entered in the text area, are also caught by the example window. This is a slightly annoying bug, but not a release blocker, |
Despite the fact that floooh/sokol#822 is now closed, it has not resolved our problems with the moving rectangle example in the web playground:
When I build tophat with the official Sokol, the text area doesn't receive any keystrokes at all -- they are all caught by the example window.
When I return
false
from_sapp_emsc_key_cb()
, all keys are caught by both the text area and the example windowBuilt with Emscripten 3.1.10.
The text was updated successfully, but these errors were encountered: