> > >> > 1. To better see what was going on in the Form>>#traceOutlines
> > >> > method, I inserted a few lines like "outer asMorph openInWorld." The
> > >> > morphs that came out were on the order of 2 to 3 times bigger on the
> > >> > screen than the original appeared in the viewport. Why is that?
> > >>
> > >> To avoid 1 pixel shapes which are problematic.
> > >
> > > This must be a problem for the later Subdivision process. I would
> > > guess that a 1 point polygon should work okay for the image->polygon
> > > extraction.
> > No, it's an issue in the tracer. If you want to try it simply scribble a
> > number of overlapping 1px lines and try it out. It'll happen sooner or
> > later.
> Okay, back to finding the starting point for the edge tracking. Since
> the form is scaled up times 2, then finding the starting point should
> be able to step by 2 instead of 1, right? Carefully noting that
> somewhere in the code for future reference, of course.
Putting my virtual money where my mouth is, I ran MessageTally on the
T3DSubdivision class>>make3DMeshFrom:style: process before and after
this change, using the goat sketch from Croquet Jasmine as the
baseline image. Making these changes saved about 100 msec on my PC
and the Form>>traceOutline: method's contribution went from 7.3% down
to 4.6%, which is all probably within the realm of measurement error.
I'll keep plodding on ...