| |
In lugnet.cad, Don Heyse wrote:
> In lugnet.cad, Kevin L. Clague wrote:
> > In lugnet.cad, Eric Albrecht wrote:
> > > In lugnet.cad, Jaco van der Molen wrote:
> > > > OK, here goes.
> > > > When an assembly is too large to fit on the page, LPub crops the image.
> > > > When one drags the assembly image to another position LPub does not redraw
> > > > the image.
> > > > See:
> > > > http://www.binarybricks.nl/test/redraw.html
> > >
> > > Thanks, that's exactly what I meant. I do instructions for multi thousand
> > > part models, so it is quite common for the assembly not to fit on the page.
> > > The workaround I have used so far is to make my own custom assembly images
> > > from LView and them manually put them in the final PDF file. That's what I
> > > did <http://www.brickshelf.com/cgi-bin/gallery.cgi?f=381742 here>.
> >
> > In the case of L3P and POV-Ray, there was the ability for look at coordinates
> > so that you could control what is the center of the viewed image.
>
> I'm not sure what you mean by this. Both LDView and ldglite have ways
> to share the coordinates used for a particular viewpoint. Something like
> this:
>
> http://ldglite.sourceforge.net/ldglitepov.html
>
> Or do you just want a way to set the "look at" point on the command line.
> I believe that's also available in both programs.
>
> > If such a mechanism were to exist in LDView and LDGLite, LPub could support
> > that. This combined with the renderers cropping the image to a known size,
> > would meet your needs.
> >
> > I certainly understand the need. Imagine trying to do building instructions
> > for 25 foot buildings. Adam Tucker asked me about this issue years ago at
> > the event that became Brickworld.
> >
> > Kevin
LPub knows what parts are added at each step. LPub could find the min/max
locations of all parts added and have the look at coordinate be (min_x+max_x)/2,
(min_y+max_y)/2, (min_z+max_z)/2. This would give a general idea of where to
look.
One question is, though can I do this all the time, or should I do it as a
special case? LPub always find the min/max (for all dimensions) for the parts
in the model, and then centers the model on (min_x+max_x)/2, (min_y+max_y)/2,
(min_z+max_z)/2. Maybe now I center it on the "center" of the added parts.
I'll have to play with it and see what I can come up with. I've been away from
LPub for a while and it is hard to ramp back up, but that portion of the code is
pretty straightforward.
Kevin
|
|
| |
In lugnet.cad, Kevin L. Clague wrote:
<snip>
> > > > > When an assembly is too large to fit on the page, LPub crops the image.
> > > > > When one drags the assembly image to another position LPub does not redraw
> > > > > the image.
> > > > > See:
> > > > > http://www.binarybricks.nl/test/redraw.html
> > > >
> > > > Thanks, that's exactly what I meant. I do instructions for multi thousand
> > > > part models, so it is quite common for the assembly not to fit on the page.
> > > > The workaround I have used so far is to make my own custom assembly images
> > > > from LView and them manually put them in the final PDF file. That's what I
> > > > did <http://www.brickshelf.com/cgi-bin/gallery.cgi?f=381742 here>.
> LPub knows what parts are added at each step. LPub could find the min/max
> locations of all parts added and have the look at coordinate be (min_x+max_x)/2,
> (min_y+max_y)/2, (min_z+max_z)/2. This would give a general idea of where to
> look.
>
> One question is, though can I do this all the time, or should I do it as a
> special case? LPub always find the min/max (for all dimensions) for the parts
> in the model, and then centers the model on (min_x+max_x)/2, (min_y+max_y)/2,
> (min_z+max_z)/2. Maybe now I center it on the "center" of the added parts.
>
> I'll have to play with it and see what I can come up with. I've been away from
> LPub for a while and it is hard to ramp back up, but that portion of the code is
> pretty straightforward.
>
> Kevin
Pardon me replying to my own post.....
The above may help with LPub showing the right portion of a large mode, but it
doesn't help with cropping the image size to contain what has changed, which I
think would have a significant impact on building instruction size. LEGO does
occasionally show cropped portions of whole model images, but they don't do that
as a general rule. But then again, they don't generally sell 25 foot tall Sears
towers.
LPub already has a mechanism for identifying where callouts are added to a model
so it can place the arrows from the callout to the center of the callout usage.
I suppose it could do a similar thing for "parts added in this step" and crop
the image to contain those. I'm pretty sure that would not be the default
behavior though. Egads, more features.
I gotta get through the backlog of bugs first.
Kevin
|
|
| |
In lugnet.cad, Kevin L. Clague wrote:
>
> The above may help with LPub showing the right portion of a large mode, but it
> doesn't help with cropping the image size to contain what has changed, which I
> think would have a significant impact on building instruction size. LEGO does
> occasionally show cropped portions of whole model images, but they don't do that
> as a general rule. But then again, they don't generally sell 25 foot tall Sears
> towers.
>
> LPub already has a mechanism for identifying where callouts are added to a model
> so it can place the arrows from the callout to the center of the callout usage.
> I suppose it could do a similar thing for "parts added in this step" and crop
> the image to contain those. I'm pretty sure that would not be the default
> behavior though. Egads, more features.
>
> I gotta get through the backlog of bugs first.
No rush Kevin. There are probably not too many of us making instructions for
models of this size, and we at least have (painful) workarounds in the interim.
If you never get to it, I'm still very thankful for LPub, and if you do get to
it, you are just that much more awesome.
I've always thought that you should test out large LPub models by making
instructions for your pneumatic hexapod and then giving them to me. ;-)
Eric
|
|
| |
In lugnet.cad, Eric Albrecht wrote:
> No rush Kevin. There are probably not too many of us making instructions for
> models of this size, and we at least have (painful) workarounds in the interim.
> If you never get to it, I'm still very thankful for LPub, and if you do get to
> it, you are just that much more awesome.
As a matter of fact I am creating buildinginstructions for a model that
eventually goes of the page, but for now I just scale down the assembly size as
the model grows.
But I totally agree with Eric: no rush and thanks for LPub!
Jaco
|
|
| |
In lugnet.cad, Eric Albrecht wrote:
> In lugnet.cad, Kevin L. Clague wrote:
> >
> > The above may help with LPub showing the right portion of a large mode, but it
> > doesn't help with cropping the image size to contain what has changed, which I
> > think would have a significant impact on building instruction size. LEGO does
> > occasionally show cropped portions of whole model images, but they don't do that
> > as a general rule. But then again, they don't generally sell 25 foot tall Sears
> > towers.
> >
> > LPub already has a mechanism for identifying where callouts are added to a model
> > so it can place the arrows from the callout to the center of the callout usage.
> > I suppose it could do a similar thing for "parts added in this step" and crop
> > the image to contain those. I'm pretty sure that would not be the default
> > behavior though. Egads, more features.
> >
> > I gotta get through the backlog of bugs first.
>
>
> No rush Kevin. There are probably not too many of us making instructions for
> models of this size, and we at least have (painful) workarounds in the interim.
> If you never get to it, I'm still very thankful for LPub, and if you do get to
> it, you are just that much more awesome.
Thanks Eric.
>
> I've always thought that you should test out large LPub models by making
> instructions for your pneumatic hexapod and then giving them to me. ;-)
Well, let me tell you, that the hardest part about the pneumatic walkers is
getting all hoses on correctly. It is even harder within LDraw and LSynth! I
hear there is a new LSynth out there that produces much smaller files than it
used to though! LSynth is being better maintained than LPub, thanks to Don and
Willy.
>
> Eric
Kevin
|
|
| |
In lugnet.cad, Jaco van der Molen wrote:
> In lugnet.cad, Eric Albrecht wrote:
> > No rush Kevin. There are probably not too many of us making instructions for
> > models of this size, and we at least have (painful) workarounds in the interim.
> > If you never get to it, I'm still very thankful for LPub, and if you do get to
> > it, you are just that much more awesome.
>
> As a matter of fact I am creating buildinginstructions for a model that
> eventually goes of the page, but for now I just scale down the assembly size as
> the model grows.
Bringing this feature request back to life ... I'm working on a project now
that's 45 bricks tall.
I'd love the ability to reposition the image inside the crop window, or specify
if I'd like the top, bottom, or both (current behavior) to be cropped when the
model is too big for a page.
- Robert
|
|
|
