TextureSpriteRenderer mishandles x and y for single sprites

Issue #20 resolved
otus created an issue

The docstring for TextureSpriteRenderer says x and y are used as absolute position when a single TextureSprite is passed, but the code actually renders to an empty rect (i.e. nowhere) instead.

Testcase: add x=10, y=10 to the render call in helloworld.py example and run it with the -hardware switch.

Suggested fix is here: https://bitbucket.org/otus/py-sdl2/commits/5c5ad73975c4460a2337f081256777ec5f7ad2b9

Comments (1)

  1. Log in to comment