|
| | 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)
| | | | Re: Inline POV-Ray code?
|
| (...) Well, if thats how you really feel, then why even bother to "write up a spec/reference page on 0 IFDEF" at all. The instant you put the line: 0 IFDEF <code> in a part file you're blessing a non-ldraw extension. The <code> is by definition a (...) (23 years ago, 28-Feb-02, to lugnet.cad.dev, lugnet.cad.ray)
| | | | Re: Another stupid part-authoring question (Primo?!?)
|
| (...) Yes, the stud is hollow. The studline substitution would leave a hole 56 (or at least 48) LDU across... big enough to fit a microfig-scale capital ship. -- Tony Hafner www.hafhead.com (23 years ago, 28-Feb-02, to lugnet.cad.dev)
| | | | Re: Inline POV-Ray code?
|
| In lugnet.cad.dev, Don Heyse writes: [snipped things down a bit] (...) Generally, yeah. But mostly to the extent that I haven't thought it through enough. (...) That could work, but IMO only pushes the issue to the side. To some extent, LDraw.org (...) (23 years ago, 28-Feb-02, to lugnet.cad.dev, lugnet.cad.ray)
| | | | Re: New tool: LDDesignPad 0.3 for LDraw
|
| Hello Ryan, i looked at the problem and you are right. I will fix it in the next version because current one is almost bug-free and in want ti implement one or two more features. Thanx for telling Carsten "Ryan Farrington" <ryanjf@ifriendly.com> (...) (23 years ago, 28-Feb-02, to lugnet.cad, lugnet.cad.dev)
| |