 | | Re: L3P user primitive substitution
|
|
(...) [snip] (...) [snap] (...) Nod, right. INCLUDE has been mentioned before, in other contexts, and I'm generally in favor of it. But I'd rather discuss that in a separate thread - IF[N]DEF/ELSE/ENDIF wouldn't depend on INCLUDE. (although, for (...) (23 years ago, 19-Dec-01, to lugnet.cad.dev)
|
| |
| | Re: L3P user primitive substitution
|
|
(...) Well yes, but I wasn't just thinking about POV. I thought that was your point in changing the syntax. The 0 INCLUDE meta-command could be used to install custom colors much like the ldliterc.dat file. I'm sure there are plenty of other non-POV (...) (23 years ago, 18-Dec-01, to lugnet.cad.dev)
|
| |
| | Various Questions . . .
|
|
Okay I'm new to the whole LDraw thing so bear with me. I'm trying to model one of my creations and I've discovered two of the parts are not available. First of all, what is the process to get a part made? Can I produce a part myself and what (...) (23 years ago, 18-Dec-01, to lugnet.cad.dev)
|
| |
| | Re: L3P user primitive substitution
|
|
(...) In general, that's an interesting thought. But in this case, I don't think it's necessary - POV already has an include statement (IIRC). Of course, allowing the use of such a statement raises another issue: is it alright to distribute (...) (23 years ago, 18-Dec-01, to lugnet.cad.dev)
|
| |
| | Re: L3P user primitive substitution
|
|
(...) Just a thought. If the POVRAY (or whatever) sections get too big, would it make sense to add 0 INCLUDE meta-command so the LDRAW only programs don't waste time parsing? Then the POV specific versions could be distributed separately from the (...) (23 years ago, 17-Dec-01, to lugnet.cad.dev)
|
