Subject:
|
Re: LPub whish list
|
Newsgroups:
|
lugnet.cad
|
Date:
|
Thu, 9 Feb 2006 08:47:25 GMT
|
Viewed:
|
2607 times
|
| |
|
|
In lugnet.cad, Kevin L. Clague wrote:
> > - But of course the best solution would be to get only one set of instruction
> > for each submodel type. A completed image of the sub-model to be built along
> > with an instance count would make things clear
> > (http://www.brickshelf.com/gallery/Philo/Misc/LpubWish/sub-model_image.png)
>
> This would of course be optional because it is not always used. We get a half
> dozen or more meta-commands for describing the placement of said image (he says
> because LPub already has dramatically more meta-commands than any other
> program).
I do understand your concern. But it would be a nice feature ;o) And in line
with a lot of official LEGO BI.
> >
> > - Possibility to add some text annotations to the part list or BOM
> > (http://www.brickshelf.com/gallery/Philo/Misc/LpubWish/parts_per_step.png). This
> > allows to add lenth information to cables and hoses. It could be implemented as
> > an additionnal optionnal string argument to the LPUB PLI BEGIN SUB command.
>
> Hmmm...... then we'll need placement description for that too?
Maybe the "LPUB [BOM|PLI] PART MARGINS x y" that already define the distance
from annotation string for axle length would be enough?
>
> >
> > - In multi-step per page mode, having the option to get a part list for each
> > step instead as for each page. For large models, pages need to be big so you get
> > many steps on the first pages to fill them. Finding and identifying parts is
> > difficult with large PLI. For example here
> > http://www.brickshelf.com/gallery/Philo/Misc/LpubWish/parts_per_step.png I had
> > to add text to the step images to clearly identify tubes even though they were
> > added at a different step.
>
> Yup, I understand this request.
Syntactically it could be a simple switch added to the MULTI-STEP metacommand,
with alignment accounted by normal PLI placement. In fact it could be implicit,
if PLI placement is page relative the pli would be for the entire page, if
placement is ASSEM relative there would be a PLI for each step.
>
> >
> > - In multi-step per page mode it would be nice to be able to control alignement
> > of steps on different rows (columns). Here
> > http://www.brickshelf.com/gallery/Philo/Misc/LpubWish/alignment.png I would have
> > prefered to get all rows right-aligned.
>
> Currently I assume center justification..... right and left make sense too.
And up/down for vertical steps layout.
> >
> > - An interesting possibility would be able to zoom on a part of a big model in a
> > callout, as I did here:
> > http://www.brickshelf.com/gallery/Philo/Misc/LpubWish/zoomed_callout.png. To do
> > this, I used a smaller model callout and buffer exchanges to hide the big model.
> > Workable, but I still miss the possibility to crop the image to some dimension
> > to make the user understand that it's a partial view.
>
> Well, at some point, manual user post processing needs to be the solution.
Well... you are probably right for this one ;o)
> I'll add one to the list:
>
> Allow a given step/multi-step to span two adjacent pages.
Yes, that would ease layout of big models.
> Philo,
>
> Do you own C++ Builder 6?
No. I have access to a very old Borland compiler, and to Visual C++ 6. But I am
not fluent at all with these tools...
Philo
|
|
Message is in Reply To:
 | | Re: LPub whish list
|
| (...) I'll have to test this to see what is going on. (...) dozen or more meta-commands for describing the placement of said image (he says because LPub already has dramatically more meta-commands than any other program). (...) Hmmm...... then we'll (...) (20 years ago, 8-Feb-06, to lugnet.cad)
|
3 Messages in This Thread:
 
- Entire Thread on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
|
|
|
|
