Subject:
|
Re: L3P-Bug using LGEO
|
Newsgroups:
|
lugnet.cad.dev
|
Date:
|
Mon, 14 Nov 2005 16:13:11 GMT
|
Viewed:
|
2503 times
|
| |
|
|
I agree and disagree with this.
I agree that it would be good (for now) if L3P only substituted LGEO parts for
files with a .dat extension. Or, even better, if (a) the file being substituted
has the UNOFFICIAL/LDRAWORG meta-statement and states it is a part or (b) is
located in the ldrawparts directory.
I disagree because the dat and ldr extensions do not indicate the type of
content in the file (except that it’s an LDraw file). I imagine if we ever
break backwards compatibility in the part library, we’ll switch all the files to
.LDR extensions.
Steve
In lugnet.cad.dev, Willy Tschager wrote:
| |
hi lars,
looks like L3P doesn’t distinguish between part-files (.dat) and scene-files
(.ldr) when I use LGEO parts.
have a look at the following pic. when I render a .mpd (which containes the
subfile 926.ldr refering to the sets number) without LGEO I get a fine
result:
using LGEO-parts L3P substitutes the subfile 926.ldr with part
“32014 -
Technic Angle Connector #6” ‘cos “lg 0926.inc” has an inbuild
move-to
command (lg 0926 moved to lg 32014) to the Technic
Angle Connector #6:
you can download the related .mpd and .pov from:
http://www.holly-wood.it/tmp/l3p-bug.zip
I’m well aware that LGEO gets more and more outdated, but because of the
fantastic quality of the parts I’d like to stick to them as long as I can.
it
would be great if L3P could distinguish between .dat and .ldr ... and
use
anton raves parts for those not available in LGEO ;-)
bye, w.
|
|
|
Message has 4 Replies:
 | | Re: L3P-Bug using LGEO
|
| (...) Isn't there an official order of preference for where a file comes from (eg. check MPD firsrt, directory second and parts directory third)? If so then the most sensible way of processing would be to go through that, which would ensure no (...) (19 years ago, 14-Nov-05, to lugnet.cad.dev, FTX)
| | | Re: L3P-Bug using LGEO
|
| (...) I agree with that - it's much easier for the user to eliminate such conflicts (eg call the set file set-926.ldr) than expect the software to make such decisions for you. ROSCO (19 years ago, 14-Nov-05, to lugnet.cad.dev, FTX)
| | | Re: L3P-Bug using LGEO
|
| (...) Surely the very fact it is .ldr instead of .dat differentiates it from the lego parts. MLCad doesn't recognise 3010.ldr as a valid part, and it allows both blah.dat and blah.ldr in the same mpd file. (19 years ago, 14-Nov-05, to lugnet.cad.dev)
| | | Re: L3P-Bug using LGEO
|
| In lugnet.cad.dev, Steve Bliss wrote: [snip-snap] (...) hmm ... I always understod .ldr as scene file and .dat just for parts. at least this was what I thought reding from tim's post back in 2001: (URL) extension change is just that. Nothing changes (...) (19 years ago, 15-Nov-05, to lugnet.cad.dev)
|
Message is in Reply To:
| | L3P-Bug using LGEO
|
| hi lars, looks like L3P doesn't distinguish between part-files (.dat) and scene-files (.ldr) when I use LGEO parts. have a look at the following pic. when I render a .mpd (which containes the subfile 926.ldr refering to the sets number) without LGEO (...) (19 years ago, 14-Nov-05, to lugnet.cad.dev, FTX)
|
19 Messages in This Thread:
 
  
- Entire Thread on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
This Message and its Replies on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
|
|
|
|
