Open GoogleCodeExporter opened 9 years ago
this problem is new, and it only happens with the grossini png. maybe theres
some
problem with pyglet? if not, i have no cllue as how to fix it.
Original comment by lucio.to...@gmail.com
on 23 Apr 2008 at 9:31
maybe u know something about it?
Original comment by lucio.to...@gmail.com
on 23 Apr 2008 at 9:32
I get rendering errors with that sample, so it's hard to tell, but it looks
like a
standard texture magnification issue. Perhaps the change being observed is a
switch
from pyglet.image.load (which uses a single texture) to pyglet.resource.image
(which
may pack multiple images onto one texture).
I suspect the pyglet.resource module may need to be better about borders.
Original comment by r1chardj0n3s
on 25 Apr 2008 at 10:57
I also see the border sometimes with other png's I use here
Original comment by twoelz
on 15 May 2008 at 12:54
I also see similar border (usually at one side only) sometimes with
cocos.text.Label.
I also noticed that the label text is sometimes slightely clipped at the bottom
of
the letters. This also happens in the python interpreter layer (it works as a
test
case): try typing 'gOC' and check if the bottom of the letters is flat,
slightely
clipped.
Original comment by twoelz
on 15 May 2008 at 2:45
oh, i forgot to mention, sometimes text is clipped below, sometimes above the
letters, depending on where the text is. the letter change slightely in shape
(thicker, thinner) from one line to another and even within the same line.
seems to
have something to do with scaling and/or antialiasing, im not sure.
Original comment by twoelz
on 15 May 2008 at 3:17
someone should do a small test case using pyglet only and submit it...
Original comment by lucio.to...@gmail.com
on 15 May 2008 at 7:56
Not taking ownership of this issue.
Original comment by r1chardj0n3s
on 13 Feb 2010 at 2:08
... though I will note that I fixed a border issue in the cocos.tiles module by
setting an
appropriate texture clamp on the cell textures. This may also work for
troublesome
sprites...
Original comment by r1chardj0n3s
on 16 Feb 2010 at 6:10
Original issue reported on code.google.com by
lucio.to...@gmail.com
on 23 Apr 2008 at 9:12