|
|
 | | Re: L3P Options?
|
| (...) That all sounds perfect. I really like the idea of L3Begin.inc and L3End.inc as well. I think that is a brilliant solution. As for the inline/not-inline option, for L3Begin, L3End and L3Colours I think it should default to inline but be (...) (20 years ago, 14-Apr-05, to lugnet.cad.ray)
| | | | | Re: L3P Options?
|
| (...) I would think if any "system-wide" or "shared" files are included they should by default be inlined, as any changes would affect (maybe deterimentally) previous renders. Any project-specific files I create always get saved locally, so I see no (...) (20 years ago, 13-Apr-05, to lugnet.cad.ray)
| | | | | Re: L3P Options?
|
| (...) I'd be willing to try and give it a go. I'm still working on a new front end to it (allows automation and a few other things specified in the draw file itself) The current build is at: (URL) Dean Earley, Dee (dean@earlsoft.co.uk) irc: (...) (20 years ago, 13-Apr-05, to lugnet.cad.ray)
| | | | | Re: L3P Options?
|
| (...) Sure, I already had you and a few others in mind, exactly because I'm aware of your "dissection" and others heavy color redefinition. But if anyone else is ready to spend some time with a beta, and give some feedback, please send me a mail. (...) (20 years ago, 13-Apr-05, to lugnet.cad.ray)
| | | | | Re: L3P Options?
|
| (...) There will be the following include file options: -ib<file> include file at beginning of POV file -ic[<file>] no camera, optional include file -il[<file>] no lights, optional include file -ie<file> include file at end of POV file But are you (...) (20 years ago, 13-Apr-05, to lugnet.cad.ray)
|
|
