Subject:
|
Re: FYI MPD not good with LPub
|
Newsgroups:
|
lugnet.cad
|
Date:
|
Mon, 14 Apr 2003 17:28:36 GMT
|
Viewed:
|
659 times
|
| |
|
|
Sounds like there needs to be a reserved word (or whatever it's called in
LDraw-ese) for a Time/Date stamp, perhaps like a "0 LastChangeTD 04-14-2003
10:14:27", for each sub model.
Kevin & Mike, can you guys get right on that! ;)
SteveB
In lugnet.cad, Kevin L. Clague writes:
> I wanted folks to know that MPD and LPub work, but are not an optimal
> combination.
>
> LPub performs a date stamp comparison of the dat file it is processing at a
> given sub-model-level, and the images rendered for that dat file. If the
> files don't exist, or the dat file is newer than the images, the images are
> rendered to bring them up to date.
>
> When you make any change to a model described in an MPD file, the date of
> the MPD file changes, so it is automatically newer than *all* your rendered
> images. When LPub goes to process your MPD file, it extracts the individual
> files from the MPD, and the extracted files are by definition newer than
> *all* your rendered images. So if you work with MLCad using MPD, LPub will
> *always* want to render *all* your images.
>
> If you work the old fashioned way, if you make a change to a given DAT file,
> only the images associated with that particular DAT file are rendered. A
> *huge* time saver.
>
> MPD is great for shipping files around as a group, but not great for keeping
> track of what changed and what needs to get rendered.
>
> Kevin
|
|
Message is in Reply To:
 | | FYI MPD not good with LPub
|
| I wanted folks to know that MPD and LPub work, but are not an optimal combination. LPub performs a date stamp comparison of the dat file it is processing at a given sub-model-level, and the images rendered for that dat file. If the files don't (...) (21 years ago, 14-Apr-03, to lugnet.cad)
|
2 Messages in This Thread:
 
- Entire Thread on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
|
|
|
|
