[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Octave-bug-tracker] [bug #45494] Patches have spurious (antialising) li

From: Dan Sebald
Subject: [Octave-bug-tracker] [bug #45494] Patches have spurious (antialising) lines in vector printout
Date: Thu, 20 Jul 2017 16:36:22 -0400 (EDT)
User-agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:52.0) Gecko/20100101 Firefox/52.0

Follow-up Comment #30, bug #45494 (project octave):

In an editor, I removed all the black lines from foo.svg.  There are no cracks
or stitching lines visible in Inkscape.  Is it because these are overlapping
triangles?  One has to not reassemble the blue triangle to disrupt the
hidden-surface layering.  But one could, in fact, include the red rectangle as
part of a tessellation with the blue triangles around it.  Nothing is lost in
that case, as this is 2D data and the viewer isn't going to rotate the
surface/view angle.

For gnuplot, breaking up the intersecting shapes into smaller shapes for layer
order is pretty straightforward.  It's more a matter of all the book keeping
that has to be done.  The code is C, so not convenient C++ lists.

BTW, regarding this foo.svg example, zooming into the image in the viewer or
Inkscape shows a bad joining of lines where the red and blue triangles
intercept.  I've attached a screen capture.  Through trial and error I
identified the two lines as these:

<polyline fill="none" stroke="#000000"
stroke-width="0.5" stroke-linecap="butt"
stroke-linejoin="miter" points="298.08,208.44
<polyline fill="none" stroke="#000000"
stroke-width="0.5" stroke-linecap="butt"
stroke-linejoin="miter" points="299.721,209.231

It looks to me like the x,y-coordinates of the point that is supposed to match
at the intersection of the blue/red triangles at that edge aren't being
computed the same:



Reply to this item at:


  Message sent via/by Savannah

reply via email to

[Prev in Thread] Current Thread [Next in Thread]