 | | Re: Inline POV-Ray code?
|
|
(...) No, I meant the POVRay code referring to L3P-generated objects. By allowing this code in official part files, we'd be endorsing language that hasn't been generally discussed and reviewed. Not that I see any particular problem with the code. (...) (23 years ago, 28-Feb-02, to lugnet.cad.dev, lugnet.cad.ray)
|
| |
| | Re: Inline POV-Ray code?
|
|
(...) Which part of it aren't you keen about? Is it all the extra stuff in the dat file? If so, then perhaps this is a good time to dredge up my 0 INCLUDE suggestion yet again. ;) (URL) (23 years ago, 27-Feb-02, to lugnet.cad.dev, lugnet.cad.ray)
|
| |
| | Re: Inline POV-Ray code?
|
|
(...) OK. I'll write up a spec/reference page on 0 IFDEF. It will include the following metacommands: 0 IFDEF <code> 0 IFNDEF <code> 0 ELSE 0 ENDIF Should there be a 0 ELSEIFDEF and/or 0 ELSEIFNDEF? (...) Steve (23 years ago, 27-Feb-02, to lugnet.cad.dev, lugnet.cad.ray)
|
| |
| | Re: Problem with Seam Width
|
|
(...) If you are thinking about making instructions, I would strongly suggest at least checking out MEGAPOV's find_edges function. Even without using the LGEO library, the instructions output is far and away the best I have seen so far for (...) (23 years ago, 23-Feb-02, to lugnet.cad.ray)
|
| |
| | Re: Problem with Seam Width
|
|
(...) The LGEO parts have rounded edges. That's why it doesn't make sense to have a "seam" between the parts. And Mega-POV will not be able to identify the edges simply because there are no edges! I you want to use the edges highlighting function in (...) (23 years ago, 23-Feb-02, to lugnet.cad.ray)
|
