Skip to content

Expose native sdl functionality #3392

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

Closed
amengede opened this issue Mar 26, 2025 · 2 comments
Closed

Expose native sdl functionality #3392

amengede opened this issue Mar 26, 2025 · 2 comments

Comments

@amengede
Copy link

Pygame is a wrapper around SDL, and it’s great! However advanced users would like to be able to fetch the underlying SDL functions.

Examples:

getting the address of an opengl procedure not exposed by pyopengl

Getting the raw surface from a window for vulkan rendering

A quick fix could be to expose the raw function pointer, which users could manage themselves with something like FFI.

@Starbuck5
Copy link
Member

However advanced users would like to be able to fetch the underlying SDL functions

I'd think advanced users would like to be able to use underlying SDL functionality, I don't really see what you mean about fetching.

getting the address of an opengl procedure not exposed by pyopengl

OK I sorta get what you mean now. You mean like #3285 ?

Getting the raw surface from a window for vulkan rendering

Sure, someone could work on Vulkan support but I don't think it's priority at all. I'm skeptical people will actually use it, and it seems like it would take substantial contributor effort. It's quite strange actually that I'm unaware any of feature requests for vulkan support ever, and then you and the author of #3393 mention it on the exact same day.

To make this issue more actionable I would appreciate more specific things about what you want exposed (like SDL function names) and why.

@Starbuck5
Copy link
Member

I referenced a PR that seems related to what you're bringing up, #3285. What I didn't notice is that PR was raised in response to your own other issue #3284.

I'm going to close this one as a duplicate of that, because the other issue is much more specific and actionable.

@Starbuck5 Starbuck5 closed this as not planned Won't fix, can't repro, duplicate, stale May 11, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants