|
|
 | | Re: Inline POV-Ray code?
|
| (...) Huh...? This is getting too complicated, lost me! Most of you have seen what I have done with adding POV part descriptions to parts. I believe that I was using them correctly with the "established" methods. To make much change would be too (...) (23 years ago, 5-Mar-02, to lugnet.cad.dev, lugnet.cad.ray)
| | | | | Re: Inline POV-Ray code?
|
| (...) No big deal. I just wasn't sure which nut you were shelling. :) (...) Hmm. The problem is that there would be a lot of cases - we've already got a way to handle general stuff (by creating 'primitive' files). And my (general) preference is to (...) (23 years ago, 4-Mar-02, to lugnet.cad.dev, lugnet.cad.ray)
| | | | | Re: Inline POV-Ray code? [DAT]
|
| I see now that your problem is difficult to solve. Sorry I tried to put it into a nutshell, Steve. My preference would be to design an auxiliary file for each case, and markup the LDRAW part in a very general way, so that future programs could (...) (23 years ago, 1-Mar-02, to lugnet.cad.dev, lugnet.cad.ray)
| | | | | 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)
| | | | | 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)
|
|
