Marko Zivic
Marko Zivic
I added same warning, docs and tests to `draw.rect` and `draw.arc`
Sure, here it comes.
Why is normalizing input rects bad: - Arc can be non-symmetrical, so if its rect is normalized, should it be mirrored? - Normalize function would have no purpose, because every...
Additional extreme test for new changes ```py import pygame import numpy as np def curve_points(a, b, pea, t): sin_p = np.sin(pea) cos_p = np.cos(pea) x = a * np.cos(t) y...
Implementing line width is much more complex, because it has to grow inwards. The problem is in finding points inside polygon, and this is not simple thing. There is a...
Also, note on merging `draw.aa` into `draw.`: This would require almost all draw functions to be merged: line, lines, circle, ellipse, polygon It will not make much problems in c...
> @mzivic7 I see this version has the filled argument. Do you plan on replacing it with a width, based on your testing, or do you think it's not possible/not...
> Maybe I didn't see correctly, why is the PR reverting the changes of `Coordinate` to `Point` ? Forgot to sync all my branches. Sorry.
> It looks like the change is clipping off the right hand side for this test comparing the draw polygon 'diamond' versus the 'gfxdraw' one: Actually its not `draw.aapolygon` issue....
Ok to fix it I just have to disable my overlapping-aalines-fix when this and/or previous point coordinates are ints. Should I: - Open new PR with new branch for this...