To LUGNET HomepageTo LUGNET News HomepageTo LUGNET Guide Homepage
 Help on Searching
 
Post new message to lugnet.cad.devOpen lugnet.cad.dev in your NNTP NewsreaderTo LUGNET News Traffic PageSign In (Members)
 CAD / Development / 9670
9669  |  9671
Subject: 
LPub updates
Newsgroups: 
lugnet.cad.dev
Date: 
Mon, 12 Apr 2004 18:33:16 GMT
Viewed: 
1472 times
  
Hi,
  A long overdue fix for Bill of Materials images is working.  Jake I'm really
sorry that this took so long to fix, especially in light of the grief you got
for *not* having BOM images in your book.

  I've also modified LPub to use subdirectories for all the generated files
(temporary or permanent).  These are the directories:

  LDraw, POV, Images, Layout, HTML

  This allows me to fix problems with LSynth being run by LPub, because I can
happily modify the LDraw files in the LDraw directory, without ever having to
worry about modifying the original files, or modifying file names to add
synthesis stuff to it.  Basically MPD files are expanded into the LDraw
directory, Non-MPD models are copied into the LDraw directory.  If synthesis is
enabled, then the files in the LDraw directory will be files post synthesis.
Thanks Jennifer for giving me this hint.

  LPub is not very smart when it comes to part image databases, in that if you
change an attribute of part image database generation, LPub will only use those
values for newly generated images, and happily use previously generated images
that were probably generated with different attributes.  For example if you
change the "minimum camera distance" for part images, images that were
calculated with a previous distance will be used instead of regenerated.

  I'm going to change this behavior.  I'm adding a date stamp in LPub for part
image attributes.  If any attributes are updated using the GUI, the date stamp
will be updated.  When LPub goes to render a part image, the date stamp for the
previously generated image will be compared to the date stamp for the
attributes, and if the attributes are younger, then the image is out of date and
needs to be recalculated.

  The date stamp for part images will be recorded as the creation of a file in
the part images directory.

  I'm going to add the same date stamp compare mechanism for attributes that
affect step images, so that changes to these will force regeneration when
needed.  I've not decided about where to record the date stamp for step images.
It would seem like it needs to be kept in the local config.lpb if you are
working with a local config.lpb, or in the global if you are not.  This way the
date stamp will live across restarts of LPub.

  Feedback?

Kevin



1 Message in This Thread:

Entire Thread on One Page:
Nested:  All | Brief | Compact | Dots
Linear:  All | Brief | Compact
    

Custom Search

©2005 LUGNET. All rights reserved. - hosted by steinbruch.info GbR