Ryan C. Gordon
Ryan C. Gordon
> I suppose some control over framerate is given up? Absolutely, but I'm pretty sure all the ones doing this at the system level are doing it so you can...
Maybe it's as simple as "OPTIONALLY, you can call SDL_SetRenderCallback, but the usual ways usually work too" ... on platforms that prefer this, we take advantage of the system-level APIs....
(100%, if we do something here at all, it won't be to change this to _require_ a callback. That's a total non-starter.)
Are we just looking for something like this? I feel like there's a ton of corner cases we need to watch out for if we change this, so I want...
I believe asyncify ends up running one's code as an interpreted bytecode (in addition to WASM itself being a bytecode format as well), so it can start and stop at...
> I wonder if this is an opportunity to beef up the SDL_main functionality. I'm going to take a run at this idea and see what happens.
I hope this isn't oversimplifying the problem, but now I have the w and h calculated the same way and then bumped out by an epsilon value (1 for integers,...
Ugh, floating point is the _worst_. This seems kinda inefficient, and we'll have to wire a nextafterf implementation into our C runtime support, but it is what it is. I'll...
My hero! I saw the nextafterf commit, and it looked like a lot of work. Do you want me to finish this bug with it, or are you still going?
We'll certainly accept patches to improve this, but I think there's a _lot_ of code in SDL that assumes it's being compiled with, and depends on, Emscripten.