(2026-01-26, 23:22)N. W. Perry Wrote: Yes, the d parameter is pretty simple, just plugging in coordinates and deltas. I already do this by hand. :-) And the Bezier math is an easy formula for a computer.
Layers could be used e.g. to blend colors, giving more realistic results for multiple printing passes on real-world parts (the subject of many a Parts Tracker comment thread over the years).
TEXMAP statements can already be nested so I don't see why they couldn't be layered. I don't know how involved compositing is, though.
Hello,
Regarding SVG graphics. I use Inkscape to convert bitmap graphics into vector graphics. This works quite well. Inkscape saves the data as SVG graphics. I don't know which part or how much of the definition is used, but sometimes the absolute and relative values are not defined correctly (upper case, lower case).
But that's not the big problem. The issue is Bezier curves. You can either trace these with line segments or piece by piece using arc segments with different factors in the x and z directions. Arc segments have the advantage that primitives can be used. Then comes the triangulation.
Once I've gotten that far, why should I still use SVG?
In my opinion, bitmap graphics are only a stopgap solution and can cause problems; for example, exporting to PovRay in LDView does not work.
If primitives are used, scaling is hardly a problem thanks to the capabilities of LDView.
Before the TEXMAP specification is extended, I would consider it more useful to improve the graphics capabilities, such as color gradients.
Or functions such as for loops, parameter passing, and much more.
PostScript could serve as food for thought here.
Best regards,
Manfred