This bug report was migrated from our old Bugzilla tracker.

These attachments are available in the static archive:

• Bresenham triangle (SW_BresenhamTriangle.c, text/x-c, 2015-12-13 17:27:54 +0000, 5143 bytes)
• Bresenham triangle include (SW_BresenhamTriangle.h, text/x-chdr, 2015-12-13 17:28:48 +0000, 495 bytes)
• Bresenham triangle AA (SW_BresenhamTriangleAA.c, text/x-c, 2015-12-13 17:29:36 +0000, 8443 bytes)
• Bresenham triangle AA include (SW_BresenhamTriangleAA.h, text/x-chdr, 2015-12-13 17:29:58 +0000, 503 bytes)

Reported in version: don't know
Reported for operating system, platform: All, All

Comments on the original bug report:

On 2015-12-13 17:27:54 +0000, Marcel Bakker wrote:

Created attachment 2336
Bresenham triangle

Attempt at a Bresenham triangle that might be of use for the Software Renderer
(SDL_RenderFillRects is used to draw a h-line as drop-in)

On 2015-12-13 17:28:48 +0000, Marcel Bakker wrote:

Created attachment 2337
Bresenham triangle include

On 2015-12-13 17:29:36 +0000, Marcel Bakker wrote:

Created attachment 2338
Bresenham triangle AA

On 2015-12-13 17:29:58 +0000, Marcel Bakker wrote:

Created attachment 2339
Bresenham triangle AA include

On 2018-08-06 21:20:22 +0000, Ryan C. Gordon wrote:

Hello, and sorry if you're getting dozens of copies of this message by email.

We are closing out bugs that appear to be abandoned in some form. This can happen for lots of reasons: we couldn't reproduce it, conversation faded out, the bug was noted as fixed in a comment but we forgot to mark it resolved, the report is good but the fix is impractical, we fixed it a long time ago without realizing there was an associated report, etc.

Individually, any of these bugs might have a better resolution (such as WONTFIX or WORKSFORME or INVALID) but we've added a new resolution of ABANDONED to make this easily searchable and make it clear that it's not necessarily unreasonable to revive a given bug report.

So if this bug is still a going concern and you feel it should still be open: please feel free to reopen it! But unless you respond, we'd like to consider these bugs closed, as many of them are several years old and overwhelming our ability to prioritize recent issues.

(please note that hundred of bug reports were sorted through here, so we apologize for any human error. Just reopen the bug in that case!)

Thanks,
--ryan.