You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I would expect all of these calls to draw a line from 0, 0 to 100, 100, but neither of them do.
a and b draw nothing. c draws a line from 0, 0 to 50, 50.
functionlove.draw()
love.graphics.line(100, 100, 100, 100)
end
Since line coordinates are endpoint-inclusive, I think this should draw a single point at 100, 100.
Funny backstory: I wasted a considerable amount of time trying to find a bug in a routine that builds a huge graph; turns out all the nodes were actually connected, but some of the lines in the visualisation had duplicate points like this.
The text was updated successfully, but these errors were encountered:
For reference, there's a bit of discussion about this in #972. However I haven't decided yet if the same stance should be taken as in the original issue so I might leave this open.
I think especially when we're talking about arbitrarily generated lines, it would be very nice to have a more resilient line drawing function, and in particular the expected behaviour of drawing a point if start and end are the same simplifies things a bit (for the end user). Maybe it is unexpected for other people, though.
I would expect all of these calls to draw a line from
0, 0
to100, 100
, but neither of them do.a and b draw nothing. c draws a line from
0, 0
to50, 50
.Since line coordinates are endpoint-inclusive, I think this should draw a single point at
100, 100
.Funny backstory: I wasted a considerable amount of time trying to find a bug in a routine that builds a huge graph; turns out all the nodes were actually connected, but some of the lines in the visualisation had duplicate points like this.
The text was updated successfully, but these errors were encountered: