|
| | Re: Inline POV-Ray code?
|
| (...) Right! I have always thought of the "0 IFNDEF L3PPOV" as a way to utilize most of the normal LDraw lines (that L3P can convert to equivalent POV code) and only replace a small tricky curvy section by some POV code that would look better. This (...) (23 years ago, 28-Feb-02, to lugnet.cad.dev, lugnet.cad.ray)
| | | | Printable Parts Catalog Updated
|
| I blame the flu for the delay. For those who haven't found it yet, it has a new home: (URL) is my own domain name, so I don't foresee any address changes ever again. Enjoy. -- Patrick Sayre-Little patrick@nightsolo.net (23 years ago, 28-Feb-02, to lugnet.cad)
| | | | Re: Inline POV-Ray code?
|
| (...) When I wrote this message, I was trying to figure some rational way to mix LDraw and L3P/POV-Ray code. Something like: 0 IFNDEF L3PPOV (ldraw code) 0 ELSE 0 #if (STUDS) 0 LDRAW 0 1 16 0 0 0 1 0 0 0 1 0 0 0 1 stud2.dat 0 LDRAW END 0 #end 0 (...) (23 years ago, 28-Feb-02, to lugnet.cad.dev, lugnet.cad.ray)
| | | | Re: Inline POV-Ray code?
|
| (...) I'm not following. Are you agreeing with the idea of using embedded POV-Ray code, or having separate file libraries? I *think* you agree with the second, am I right? The one thing we gain by having embedded POV-Ray code is the ability to have (...) (23 years ago, 28-Feb-02, to lugnet.cad.dev, lugnet.cad.ray)
| | | | Re: Inline POV-Ray code?
|
| In a nutshell, 'namespaces'. Switching among parts libraries to get different versions (or different data) should be an application capability, not the individual part file. (23 years ago, 28-Feb-02, to lugnet.cad.dev, lugnet.cad.ray)
| |