Anyway, recently I have discovered a small bug that only happened in very special conditions related to clipping operations. By the way, it's worthy to know that all vector based drawing operations are "clipping aware" or, in other words, shapes are drawn naturally clipped.
This problem was very subtle and affected just the bound pixels close to the clipping frame. In specific conditions, the ingenious (integer based) calculations of the renderer could need to deal with unexpected negative values, generating wrong results.
Below you can see a wrong rendering (left side) and a correct one (right side). The blue squares represent the clipping windows and the small red squares highlighted the region that failed in the left drawing.
Here I show the small regions increased 10 times in size, so you can see clearly the wrong pixels and how they were fixed in right side image.
Now my 2D anti-aliased drawing algorithm is even more precise, and it's not all. Seizing the opportunity and the knowledge I acquired these last years, I have improved the algorithm speed even more. After these recent optimizations, the drawing operations are kind of 17% faster for most cases.
P2P keeps its commitment to offer the most professional softwares, so you can generate more and more outstanding results.
Subscribe in a reader
