| |
In lugnet.cad.dev, Don Heyse writes:
> In lugnet.cad.dev, Steve Bliss writes:
> > In lugnet.cad.dev, Tore Eriksson writes:
> > > MPD Workshop cannot handle a reference to a non-existing directory, or
> > > rather, it does not create a folder if necessary.
> > >
> > > For example:
> > > http://news.lugnet.com/cad/dat/ideas/?n=171
> > > The line:
> > > 0 FILE s\41342s01.dat
> > > assumes that there already exists the folder 's\' in the target directory,
> > > or else a runtime error is generated.
> > >
> > > If I get it right, the mpd is compilant but not the software?
> >
> > Hmm. I don't remember if there was a lot of discussion about putting paths
> > on the 0 FILE line. So I won't say for absolute sure that the program
> > should allow them.
>
> FWIW both the ldlite and l3 parsers in ldglite are OK with
> paths in an MPD file. Just make sure the path in the 0 FILE
> line matches the path on the type 1 line that pulls in the
> subfile. If they don't match it reports that it can't find
> the file unless it finds it on that path on the local disk.
>
> The paths match in the example above so it works just fine.
> I've seen quite a few examples posted here where the path is
> left out of the type 1 line or the 0 FILE line. These don't
> work for me. I'm not sure if they were made manually or if
> one of the MPD programs is the culprit. Either way, I think
> we should set down some real rules on this to clear it up.
>
> Don
I don't know how ldglite and other parsers work, but I guess they don't
create files with paths and all, but rather objects somewhere in RAM, with
'filenames' just as a property.
But if you call the procedure SaveToFile(Path+FileName) to save on the disk,
then the path has to be valid.
(As an experiment, I named a subfile of an MPD file *++0GGG\\\:::00.dutt and
L3Lab had no problems with that. As long as you don't have to write it to
disk, anything seems ok.)
/Tore
|
|
Message has 1 Reply:
 | | Re: MPD spec
|
| (...) Right. Any "MPD splitter" program should include code to check that filenames and paths are valid, and either report missing paths, or create them, or ask the user before creating them, or provide options (ie, command line parameters) to (...) (22 years ago, 6-Aug-02, to lugnet.cad.dev, lugnet.cad.dev.org.ldraw)
|
Message is in Reply To:
| | Re: MPD spec
|
| (...) FWIW both the ldlite and l3 parsers in ldglite are OK with paths in an MPD file. Just make sure the path in the 0 FILE line matches the path on the type 1 line that pulls in the subfile. If they don't match it reports that it can't find the (...) (22 years ago, 6-Aug-02, to lugnet.cad.dev, lugnet.cad.dev.org.ldraw)
|
65 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
|
|
|
|
