Actually, after second thought, you are probably right. Maybe we could factor the the dialog into 3 areas, with input filter selections/adjustments, algorithm-specific parameters, and output filtering stuff like curve smoothing. Might save a lot of space.
Bob
Bob Jamison wrote:
I think that this argument is moot, as I think that Derek and I have agreed on option 3.
Well, Jeez....
I agree with you on most things, but I'm afraid that I must disagree on this one small thing. The different tracing algorithms need different parameters. Crowding a small set of "user friendly" params onto a mismatched set of algorithms would not work.
"Single scan" and "multi scan" are artificial ideas that I made up myself to fit my 3 input filters and 2 output filters onto Potrace. They do not map to anything but my weak idea of how to wedge Potrace into Inkscape. They are all silly tricks on how to make a black & white tracer work on color bitmaps. Potrace does NOT do color.
The next tracer (not Autotrace) that I have in mind works natively in colorspace, with no intermediate bitmap (thus no Preview) and works by tracing along lines of constant color slope.
Bob