Earlier today I found one small bug related to images written to WMF
files and posted it in launchpad. But while working on that noticed
that there was also another binary change in the output that didn't
correspond to anything I could see in the images. A careful byte by
byte comparison of EMF and WMF output from the lp988601 and current
trunk branches showed that outside of my code there has been a change,
where the paths returned on ellipse to path conversions are not as they
once were. In emf-print.cpp in the print_simple_shape() routine a print
statement was added after the call to
pathv_to_linear_and_cubic_beziers() and the loop which adds up nodes,
lines, and curves. For the exact same ellipse (long axis aligned with
x, short with y, axis ratio about 2:1) this is what was found:
nodes lines curves
lp988601 5 0 4
trunk 9 0 8
They start at the same point, but differ from there. Tried it again
with perfect circles and got the same result.
The strange thing is that there is no change at all to the geom.cpp
file, where pathv_to_linear_and_cubic_beziers() is coded.
I also checked to see if anything similar could be seen in the GUI, and
it sort of could be. Select the ellipse, select "stroke to path", then
edit points. The points on the ellipse are in different places in the
two branches, and there are different numbers of points. For lp988602
there is one point on the end of each axis plus one point in roughly the
center of each quadrant. For trunk there are the same points on the ends
of the axis, plus two points within each quadrant, and these are
clustered towards the "sharp" ends of the ellipse.
Is this change intentional???
Manager, Sequence Analysis Facility, Biology Division, Caltech