Skip to content
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

Events are not processed when using SDL 2.0.20 #301

Closed
blast007 opened this issue Jan 22, 2022 · 4 comments
Closed

Events are not processed when using SDL 2.0.20 #301

blast007 opened this issue Jan 22, 2022 · 4 comments
Labels
Milestone

Comments

@blast007
Copy link
Member

When built against SDL 2.0.20, input events are not handled, so it's not possible to use the keyboard or mouse to interact with the game. In addition, I'm not sure if events are being processed at all since I also get an unresponsive application alert, at least on Fedora 35.

So far I've tested on Fedora 35 with their included binary package and built from source, and I've also compiled from source against a self-compiled SDL 2.0.20 on Debian 11. All exhibit the problem. I have not tested on other platforms.

@blast007 blast007 added the bug label Jan 22, 2022
@blast007 blast007 added this to the 2.4.24 milestone Jan 22, 2022
@blast007
Copy link
Member Author

BZFlag breaks after this change in SDL: Move special sentinel handling inside SDL_PeepEvents()

@macsforme
Copy link
Member

For the record, this issue also manifests on macOS with SDL 2.0.20. I tested it on Mojave and Monterey, both Intel and ARM, and the issue was present in all scenarios.

@jeffpc
Copy link

jeffpc commented Feb 10, 2022

Similarly, the FreeBSD packages are affected. The game starts, but keyboard/mouse events have no effect. The package versions on FreeBSD are:

$ pkg info|egrep '(sdl|bzflag)'
bzflag-2.4.22_1                Multiplayer 3D tank battle game
sdl2-2.0.20_1                  Cross-platform multimedia development API
sdl2_image-2.0.5               Simple library to load images of various formats as SDL surfaces

@blast007
Copy link
Member Author

A workaround for this issue was added in BZFlag 2.4.24.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants