On Tue, Oct 6, 2009 at 5:06 PM, Richard Jones <[email protected]>wrote:
> On 06/10/2009, at 5:44 PM, Brian Fisher wrote: > > On Mon, Oct 5, 2009 at 4:29 PM, Richard Jones <[email protected]>wrote: > >> >> Sub-pixel rendering requires a lot of manual effort to ensure there's >> no strange visual artefacts on the borders. Hence the standard Sprite >> implementation avoids it. >> >> <snip lengthy discussion of various rendering errors and workarounds> > > The Sprite module is intended to be used by people who don't necessarily > even know what sub-pixel positioning is, let alone what the rendering > repercussions are and certainly not how to avoid them. > That sounds like a solid justification for expanding the documentation or adding an FAQ item, but not so much for restricting to integer coordinates. In the spirit of full disclosure, I will mention that all of my 2D pyglet projects to date have used a replacement sprite class, partly to gain sub-pixel positioning, and partly to gain proper animation support (i.e. seek, loop and pause). -- Tristam MacDonald http://swiftcoder.wordpress.com/ --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pyglet-users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/pyglet-users?hl=en -~----------~----~----~----~------~----~------~--~---
