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

Better support for creating your own surfaces #71

Open
lordmauve opened this issue Mar 2, 2018 · 2 comments
Open

Better support for creating your own surfaces #71

lordmauve opened this issue Mar 2, 2018 · 2 comments

Comments

@lordmauve
Copy link
Owner

@lordmauve lordmauve commented Mar 2, 2018

In lordmauve/snowgame we encountered several places where we needed to bypass Pygame Zero's APIs in order to create new surfaces, blit actors to them, and set pixels.

In some ways it was always intended that you could directly access Pygame, but I was surprised at how little Pygame Zero functionality could be used once you do.

For example, it would be useful if Actors could take a surface that they were attached to as a parameter, and optionally have it overridden in Actor.draw().

It would be useful to wrap new "Screen" objects around newly created surfaces.

It would be useful to be able to create a "Screen buffer" by copying the dimensions of a screen.

@sapoturge
Copy link
Contributor

@sapoturge sapoturge commented Jun 25, 2019

If this is done, it could also add support for Pygame subsurfaces, which would make #43 Sprite sheets easier. In the game I'm making, I use a (non-animated) tileset and subsurfaces to draw the environment. I can work on this, if you want.

@lordmauve
Copy link
Owner Author

@lordmauve lordmauve commented Jul 17, 2019

That would be great. I don't have strong views on how this would work. I'd love to see ideas!

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

Successfully merging a pull request may close this issue.

None yet
2 participants