Subject:
|
Re: MPD format
|
Newsgroups:
|
lugnet.cad.dev
|
Date:
|
Mon, 15 Mar 1999 17:09:57 GMT
|
Viewed:
|
772 times
|
| |
|
|
Paul Gyugyi wrote:
> By convention, tools like L3P and LDLite, when given an mpd
> file, will render the first subfile. The subfiles can reference
> each other.
>
> If you use an MPD file in a Type 1 line, your results will vary.
> LDLite will (I think) finish drawing the top-level file, and then
> start over drawing the first subfile of the last MPD file
> encountered.
L3P will treat an MPD file in a Type 1 line exactly as it treats
an MPD file as the main file (top-level file). L3P's nature is
recursive.
An MPD file is just another way of storing sub-files.
In stead of loading sub-files from the usual directories, some
sub-files are simply taken from the MPD file.
> I will be changing this. In version 1.7, having a type-1 line that
> specifies an MPD file will not draw anything, but just load all the
> parts into memory so they can be used later in the file. This
> would allow you to convert the PARTS directory to a single MPD file,
> and then specify "1 16 0 0 0 1 0 0 0 1 0 0 0 1 parts.dat" in your
> start-up file.
In stead of changing the well-known semantics of
"1 16 0 0 0 1 0 0 0 1 0 0 0 1 parts.dat"
to depend on the contents of parts.dat, wouldn't it be better to
use a META command? Like "0 LOADCACHE parts.dat"
/Lars
|
|
Message has 1 Reply:
 | | Re: MPD format [DAT]
|
| I think valid drawing lines before the first "0 FILE" of an MPD file should not be allowed (comments and garbage lines are OK). Either it is an MPD file, or it is not. If valid drawing lines are encountered first, well, here's an example of what (...) (26 years ago, 16-Mar-99, to lugnet.cad.dev)
|
3 Messages in This Thread:
 
- Entire Thread on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
|
|
|
|
