Thanks Travis and Chris,
This is a very interesting (and universal) approach, I could setup a special mpd for the flat shapes and additional information so it's completely extendable/customizable. And if the shapes ever become part of the library it will act like a fallback.
All this makes me want to go directly to the generating part of coding, but I have to make some changes to the internals of LDCad to allow for general path editing first.
I was thinking of using 'segments' in means of you place an additional point and assign a type to it e.g.: 'circle arc' (to go around a poly etc), 'free arc', 'straight line', 'bezier curve' or 'pass through' (LSynth like markers) . You could off-course change the type afterwards or split a segment into two etc. Finally the first and last point (in meta wise) then automatically become the end caps.
Any thoughts on that?
This is a very interesting (and universal) approach, I could setup a special mpd for the flat shapes and additional information so it's completely extendable/customizable. And if the shapes ever become part of the library it will act like a fallback.
All this makes me want to go directly to the generating part of coding, but I have to make some changes to the internals of LDCad to allow for general path editing first.
I was thinking of using 'segments' in means of you place an additional point and assign a type to it e.g.: 'circle arc' (to go around a poly etc), 'free arc', 'straight line', 'bezier curve' or 'pass through' (LSynth like markers) . You could off-course change the type afterwards or split a segment into two etc. Finally the first and last point (in meta wise) then automatically become the end caps.
Any thoughts on that?