Subject:
|
Re: Background color controls for constr and part list images
|
Newsgroups:
|
lugnet.cad.dev
|
Date:
|
Fri, 11 Apr 2003 14:21:39 GMT
|
Viewed:
|
1010 times
|
| |
|
|
Hi Jennifer,
I started on a new meta-command in LPub to address these concerns (because my
head is still spinning from the whole extension topic.)
I'm introducing a new meta-command:
0 LPUB CALLOUT BEGIN (parameters)
0 LPUB CALLOUT END
It is intened to brack sub-model usages and have these effects
1. Sub-model building step images are packet together in sequential order
into a large picture showing each individual step. You will be able to define
a maximum number of rows, or a maximum number of columns for the final image.
You will also be able to specify the maximum picture width or height so that
LPub will reduce the size of the image if you desire (while maintaining aspect
ratio.) I'm sure there are other parameters we will want as well like position
on the final output page.
2. For Part List Images, for any sub-models that are "called out" in a given
step, LPub opens the sub-model and counts up the parts in the sub-model. If
those secondary sub-models "callout" terciary (sp?) sub-models, those parts are
counted also. This way the parts used in any callouts for a given step are
listed in the part list image for the current step. If you want to prevent the
sub-model parts showing up in the step's PLI, you can put "PLIST BEGIN
IGN"/"PLIST END" around the sub-model, but inside the CALLOUT BEGIN/END. You
can of course use the sub-model's BOM to identify the parts needed just for the
callout image.
I've got the PLI part working already. I'll be working on the compound image
generation stuff over the weekend.
I'm open to input from all on the architecture outlined here.
An obviously related topic here is background image color for construction
images, PLIs and BOMs.
Kevin
In lugnet.cad.dev, Jennifer Clark writes:
>
> "Kevin L. Clague" <kevin_clague@yahoo.com> wrote in message
> news:HCrxBz.1Bso@lugnet.com...
> >
> > Let me try to restate this by example:
> >
> > Step N adds three LDraw parts, plus a sub-model. You want the part list
> > image for Step N to include the three added parts, plus all the parts • needed to
> > create the sub-model. Right?
>
> Yes, and the same for the included sub-sub-models as well.
>
> It would be good to have a control for doing this or not for each step
> including a sub-model, as there as some sub-models which are too complex to
> include in steps in this way, and therefore need their own pages in the
> instructions.
>
> So, for example, we have the step as described previously with sub-model and
> sub-submodel included in a single top level step - would "sub model
> inlining" be an appropriate term for this? :-
>
> [1] http://library.brickshelf.com/scans/8000/8460/8460-015.html
>
> Some sub-models are too large or complex for this, however. In the same
> instructions there is also a sub-model representing the crane superstructure
> which is done in the standard way, the way LPub currently does it :-
>
> [2] http://library.brickshelf.com/scans/8000/8460/8460-028.html
>
> Of course, things are not that simple! Case [2] shows a sub-model, but there
> are sub-models in this sub-model which are of course sub-sub-models, and
> those are rendered on a yellow background. Now in the case [1], with the
> sub-model and sub-sub-models directly included in the top level step, the
> equivalent level model is on a pink background.
>
> In other words, the colour of the background of a model, sub-model and
> sub-sub-model depends not only on the its explicit place in the model
> hierarchy, but also on the context. I think it goes like this:
>
> - If doing a step where there are sub-models explicitly included in that
> page such as [1], then do the background colours according to the normal
> hierarchy of inclusion.
>
> - If doing a submodel which is not explicitly included as part of a step,
> such as [2], then the hierarchy must be promoted up one level, such that the
> sub-model is rendered in the same way as the top level model, and so on.
>
> My apologies for the obscureness of this, I wish I could put it more
> succintly!
>
> Jennifer
|
|
Message is in Reply To:
17 Messages in This Thread:
  
 
 
- Entire Thread on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
|
|
|
|
