On Mon, Mar 9, 2009 at 7:29 PM, xyloidhead <[email protected]> wrote: >> >> The problem is that draw needs to cut 25 pixels from the second >> segment to draw the join. but it doesnt have enough pixels, so it does >> weird things. >> >> It is a bug, and a very nasty one. A workaround would be to only add >> lines is the movement is bigger than half the line width. ugly, i >> know. > > Ugly but bearable. I can probably modify the code to change the > movement as you suggest as mostly the line width will be quite small. > >> >> There are still issues with sharp turns. >> >> Summing it up, cocos.Draw is not ready for prime time. > > This may be true but it is way, way better than the primitive code I'd > put together to do a similar thing. So I'll keep using it. >
Then please dont forget to send me any other feedback you have. Im going to pycamp in two weeks for a sprint, and maybe i can finish this there. Lucio. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "cocos2d discuss" 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/cocos-discuss?hl=en -~----------~----~----~----~------~----~------~--~---
