ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
When developing an SDL2 application that targets a fixed logical resolution, developers often call SDL_RenderSetLogicalSize after the renderer has been created to decouple drawing coordinates from the window pixel dimensions. The documentation states that the new logical size applies to subsequent drawing operations, but it is unclear whether the function al
Context I'm building an SDL2-based UI layer that must work with screen readers on Windows, macOS, and X11. SDL_PollEvent gives me raw input and window events, but no accessibility metadata, so I currently translate SDL_WINDOWEVENT_FOCUS_GAINED and my own widget focus model into platform accessibility API calls (UI Automation, NSAccessibility, AT-SPI) myself.
The goal is to confirm that an SDL_SetEventFilter callback installed in an SDL2 application continues to function unchanged when the same source is compiled against SDL3, ensuring that unwanted input events are still suppressed without adding notification noise. However, the SDL3 migration notes have not settled whether the function signature, the SDL_Event
Our application renders its entire user interface through SDL (Simple DirectMedia Layer), drawing menus and dialogs onto a single window surface. We now need this workflow to be usable with screen readers such as NVDA and VoiceOver, not just with keyboard-only input. From what I understand, SDL is a low-level windowing and input layer: it delivers keyboard e
sdl