-
Notifications
You must be signed in to change notification settings - Fork 3.3k
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
Browser.safeSetTimeout fails to pass timeout interval setTimeout #17941
Comments
sbc100
added a commit
to sbc100/SDL
that referenced
this issue
Sep 29, 2022
Instead use the native emscripten timer API. See emscripten-core/emscripten#17941
sbc100
added a commit
that referenced
this issue
Sep 29, 2022
sbc100
added a commit
that referenced
this issue
Sep 29, 2022
sbc100
added a commit
that referenced
this issue
Sep 29, 2022
sbc100
added a commit
that referenced
this issue
Sep 29, 2022
sbc100
added a commit
to sbc100/SDL
that referenced
this issue
Sep 30, 2022
Instead use the native emscripten timer API. See emscripten-core/emscripten#17941
sbc100
added a commit
to sbc100/SDL
that referenced
this issue
Sep 30, 2022
Instead use the native emscripten timer API. See emscripten-core/emscripten#17941
sbc100
added a commit
to sbc100/SDL
that referenced
this issue
Sep 30, 2022
Instead use the native emscripten timer API. See emscripten-core/emscripten#17941
icculus
pushed a commit
to libsdl-org/SDL
that referenced
this issue
Sep 30, 2022
Instead use the native emscripten timer API. See emscripten-core/emscripten#17941
PJB3005
pushed a commit
to PJB3005/SDL
that referenced
this issue
Oct 5, 2022
Instead use the native emscripten timer API. See emscripten-core/emscripten#17941
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Compiling with emcc v3.1.16 with SDL2 included.
The compilation of SDL_AddTimer produces a timer that fails to wait any time before the callback fires because their implementation uses Browser.setSafeTimeout which doesn't pass the timeout interval through to the setTimeout call.
This appears to have been around since 607ca448f224bab0a223d60d2b7e2426df8b0d28
The text was updated successfully, but these errors were encountered: