Sam Lantinga
Sam Lantinga
Yeah, we should revisit this for SDL3. @1bsyl, with SDL's lifecycle improvements, do we still need this?
I agree with @superfury, let's move the logic for this into the application for SDL3.
After discussion, we're going to change SDL_ANDROID_BLOCK_ON_PAUSE to default to 0, and look to see if we can do something smarter in WaitEvent, which has a system specific wait call...
This patch is in (thanks @ericwa!) and I'm moving discussion for the final SDL 3.0 approach to https://github.com/libsdl-org/SDL/issues/7134.
I'm not going to have time to look at this for this milestone. Anyone who is familiar with Linux IME input, feel free to pick this up!
I still think changing the global latency is a terrible idea - there may be other reasons why the global latency is set to a particular value. BUT, this seems...
@icculus, what other reason could an SDL update have suddenly triggered this? The original poster mentioned that rolling back SDL fixed the issue for them.
Yes, I think this was the only report of this, so let's go ahead and revert for now.
> Have any of you guys even reported the issue at hand to dr_libs? I haven't, but I'm working on an SDL_mixer release and I'd rather use tested code that...
This is fixed for the 2.8.0 release.