 | | Re: L3P Warnings
|
|
(...) Bad simile, but ok then: I want pizza-pie and I respect those who want pizza XOR pie. Then let all three alternatives be available on the market. No Government Control over personal taste. I model in LDraw and render the final result in (...) (14 years ago, 2-Jul-10, to lugnet.cad.ray)
|
| |
| | Re: L3P Warnings
|
|
--snip-- (...) --snip-- By that argument you dismiss the opposite perspective. You call 'facile' on any argument, no matter how strong, that disagrees with your own position. I have a very clear argument for my position: POVray is not LDraw and to (...) (14 years ago, 2-Jul-10, to lugnet.cad.ray)
|
| |
| | Re: L3P Warnings
|
|
(...) Upload to where? If it's to a commonly-accessible LDraw-friendly site, then how do we avoid having to sift through 500 different versions of 3001.dat? And if it's to an individual's own personal site, then that's equivalent to hiding the file (...) (14 years ago, 2-Jul-10, to lugnet.cad.ray)
|
| |
| | Re: L3P Warnings
|
|
(...) I don't know. All I know is that I export a POV file and it works well. That's pretty much how I like my software to work. (...) They could upload the files they've made. In fact, I have done so before. (...) It's more like offering people the (...) (14 years ago, 1-Jul-10, to lugnet.cad.ray)
|
| |
| | Re: L3P Warnings
|
|
(...) Question my sanity if you must, but I'll have you know that I haven't used a 386 since 2008. I hadn't thought about the likelihood of a non-beta version being released, but as long as it supports the old syntax, then I don't care what kind of (...) (14 years ago, 1-Jul-10, to lugnet.cad.ray)
|
| |
| | Re: L3P Warnings
|
|
(...) LDView already has the ability to do this automatic replacement during POV export: Create a POV directory inside your LDraw directory Put p an parts directories in the POV directory Drop in POV files with the same filenames as the original (...) (14 years ago, 1-Jul-10, to lugnet.cad.ray, FTX)
|
| |
| | Re: L3P Warnings
|
|
(...) Thanks, but no, I don't get irritated so no need for yet another parameter to silence certain warnings. I was just a little worried. And if a future version of L3P will no longer support inline code, I'll probably stick to 1.4 Beta - if not (...) (14 years ago, 1-Jul-10, to lugnet.cad.ray)
|
| |
| | Re: L3P Warnings
|
|
In lugnet.cad.ray, Dave Schuler wrote: <snip> (...) See also my reply on Tore Eriksson message. It would be called 3001.pov and has the same information in it as the 'else' portion of the current dat files (although without the leading 0's, it would (...) (14 years ago, 1-Jul-10, to lugnet.cad.ray)
|
| |
| | Re: L3P Warnings
|
|
In lugnet.cad.ray, Tore Eriksson wrote: <snip> (...) alternatives. In that case I think Don is right, just ignore the warnings and keep doing what you like. I doubt Lars will stop supporting his own LDraw meta extensions altogether. (...) The thing (...) (14 years ago, 1-Jul-10, to lugnet.cad.ray)
|
| |
| | Re: L3P Warnings
|
|
(...) I think I've got a solution for you and Dave. Stop worrying about the messages. ;) No, really. The current version of L3P still does what you want, right? And I think we can safely predict that the next non-beta version of L3P is highly (...) (14 years ago, 1-Jul-10, to lugnet.cad.ray)
|
