|
LPub 2.1.0.8 is available from http://www.users.qwest.net/~kclague.
This version of LPub adds these new features:
- Sub-assembly callout image generation
- Unique construction image background colors for up to four sub-model levels.
- Proof mode to make Lpub do a dry run through the entire model
- Scroll bar for the console window
For sub-assembly callout image generation LPub packs sub-assembly step
images together into a single larger image. The callout facility provides
for four automatic step image placement schemes that provide for horizontal
(http://www.brickshelf.com/gallery/kclague/LPub/right-leg_1_00_co_0.jpg)
or vertical
(http://www.brickshelf.com/gallery/kclague/LPub/left-leg_1_00_co_0.jpg)
orientations. You can either explicitly list the steps in each row or column,
and LPub figures out the size, or you can provide a size constraint. If you
provide a limit to the X dimension, LPub figures out the Y dimension of the
image. If you provide a Y limit, LPub figures out the X dimension of the image.
LPub provides meta-commands to control the type outline around the outside
of the picture (none,rectangular or retangular with rounded corners), as
well as its color and thickness. Meta-commands control the placement
allocation scheme, the margins between images, the color and thickness of
seperators between rows and/or columns. LPub's GUI allows you to select the
font used for step numbering on a sub-model by sub-model basis.
LPub provides additions to the GUI to allow you to select construction image
background color on a sub-model level by sub-model level basis.
Feedback is always welcome.
Enjoy!
Kevin
|
|
|
In lugnet.announce, Kevin L. Clague writes:
> LPub 2.1.0.8 is available from http://www.users.qwest.net/~kclague.
>
> This version of LPub adds these new features:
>
> - Sub-assembly callout image generation
> - Unique construction image background colors for up to four sub-model levels.
> - Proof mode to make Lpub do a dry run through the entire model
> - Scroll bar for the console window
>
> For sub-assembly callout image generation LPub packs sub-assembly step
> images together into a single larger image. The callout facility provides
> for four automatic step image placement schemes that provide for horizontal
> (http://www.brickshelf.com/gallery/kclague/LPub/right-leg_1_00_co_0.jpg)
> or vertical
> (http://www.brickshelf.com/gallery/kclague/LPub/left-leg_1_00_co_0.jpg)
> orientations. You can either explicitly list the steps in each row or column,
> and LPub figures out the size, or you can provide a size constraint. If you
> provide a limit to the X dimension, LPub figures out the Y dimension of the
> image. If you provide a Y limit, LPub figures out the X dimension of the image.
>
> LPub provides meta-commands to control the type outline around the outside
> of the picture (none,rectangular or retangular with rounded corners), as
> well as its color and thickness. Meta-commands control the placement
> allocation scheme, the margins between images, the color and thickness of
> seperators between rows and/or columns. LPub's GUI allows you to select the
> font used for step numbering on a sub-model by sub-model basis.
This version of LPub does not support nested callouts, but this is in the
works. To make nested sub-model callouts work, I will provide new
meta-commands that describe the placement of a generated callout relative to
the current step image (complete with the triangles that point to where the
completed sub-assembly is placed in the step). LPub will use this
information to create a new image for the step that contains the
construction image and the callout(s) (there can be more than one). LPub
creates the deepest callout images and combined callout/step images first.
When LPub is told to create a callout for a higher level sub-assembly, it
will grab the combined callout/step images of the lower sub-assembly when
creating the new callout image. This gets you nested callout images.
One thing that will need to change is that LPub numbers its steps starting
at 0 (its a computer weenie thing), and LEGO starts its numbering at 1.
>
> LPub provides additions to the GUI to allow you to select construction image
> background color on a sub-model level by sub-model level basis.
>
> Feedback is always welcome.
>
> Enjoy!
>
> Kevin
|
|
|
(Cross posting to .inst)
In lugnet.announce, Kevin L. Clague writes:
> LPub 2.1.0.8 is available from http://www.users.qwest.net/~kclague.
>
> This version of LPub adds these new features:
>
> - Sub-assembly callout image generation
> - Unique construction image background colors for up to four sub-model levels.
> - Proof mode to make Lpub do a dry run through the entire model
> - Scroll bar for the console window
|
|
|
In lugnet.cad, Jake McKee writes:
> (Cross posting to .inst)
Thanks Jake. I knew I was forgetting something.
Kevin
>
>
> In lugnet.announce, Kevin L. Clague writes:
> > LPub 2.1.0.8 is available from http://www.users.qwest.net/~kclague.
> >
> > This version of LPub adds these new features:
> >
> > - Sub-assembly callout image generation
> > - Unique construction image background colors for up to four sub-model levels.
> > - Proof mode to make Lpub do a dry run through the entire model
> > - Scroll bar for the console window
|
|
|
It seems that rotation step does not work anymore?
> LPub 2.1.0.8 is available from http://www.users.qwest.net/~kclague.
>
> This version of LPub adds these new features:
>
> - Sub-assembly callout image generation
> - Unique construction image background colors for up to four sub-model
levels.
This is nice!!!
Jaco
|
|
|
In lugnet.cad, Jaco van der Molen writes:
> It seems that rotation step does not work anymore?
It is supposed to. Can you tell me how you are using it?
Buffer exchange and rotation steps used to not work correctly. I talked to
Michael and got it sorted out. Maybe now you are expecting it to act like
it did when it was broken?
>
> > LPub 2.1.0.8 is available from http://www.users.qwest.net/~kclague.
> >
> > This version of LPub adds these new features:
> >
> > - Sub-assembly callout image generation
> > - Unique construction image background colors for up to four sub-model
> levels.
>
> This is nice!!!
Thanks! I like it too. White, yellow and rose (?) seemed traditional, and
I added a light blue as the last level.
>
> Jaco
|
|
|
While rendering a model I got a JPEG error and LPub seems to stop.
What is that error and what can I do about it?
Jaco
|
|
|
"Jaco van der Molen" <jmolen@zonnet.nl> skrev i meddelandet
news:HDJ79v.211H@lugnet.com...
> While rendering a model I got a JPEG error and LPub seems to stop.
> What is that error and what can I do about it?
Kevin, are you using Delphi? And the jpeg unit from Borland? There is a
problem with jpeg pictures in the size range 1-2MB if I remember correctly.
I've seen it talked about in the Delphi newsgroups, but I'm not sure if
anyone has really found a fix (apart from using some other jpeg library).
I'd recommend .png instead, if that format is acceptable - the file sizes
are about the same as .jpg, but the compression is lossless - much better
pictures.
--
Anders Isaksson, Sweden
BlockCAD: http://user.tninet.se/~hbh828t/proglego.htm
Gallery: http://user.tninet.se/~hbh828t/gallery/index.htm
|
|
|
In lugnet.cad, Jaco van der Molen writes:
> While rendering a model I got a JPEG error and LPub seems to stop.
> What is that error and what can I do about it?
Jaco,
I need more spefic data than that. If you could quite the error mesage,
tell me wheher it was doing construciton images, part list images, callouts
or BOMs would help.
As always, sending me the dats (and the config.lpb) would help so I can
try to recreate the problem at my end.
>
> Jaco
Kevin
|
|
|
In lugnet.cad, Jaco van der Molen writes:
> It seems that rotation step does not work anymore?
Hi Jaco,
Thanks for the DAT info on the failing behavior. I found and fixed an
LPub bug. You can work around this bug by rearranging your DAT. Here is
part of what you sent me, starting at the beginning:
0 STEP
0 ROTSTEP -155 135 0 ABS
1 7 0 0 0 0 0 1 0 1 0 -1 0 0 3034.DAT
0 BUFEXCHG A STORE
If you rearrange things like this:
1 7 0 0 0 0 0 1 0 1 0 -1 0 0 3034.DAT
0 ROTSTEP -155 135 0 ABS
0 BUFEXCHG A STORE
Notice there was no need for the initial STEP, because there were not parts
added before the step.
Notice that ROTSTEP is a STEP that lets you specifiy rotation. So following
STEP with ROTSTEP and no intervening parts doesn't do much good either.
MLCad ignores these as steps because you added no parts. LPub was trying to
do the same, but in the process forgot to remember the rotation.
In the second draft, you get exactly the same results as your original code,
but the description is more concise (and it works around the bug in 2.1.0.8 :^)
Kevin
>
> > LPub 2.1.0.8 is available from http://www.users.qwest.net/~kclague.
> >
> > This version of LPub adds these new features:
> >
> > - Sub-assembly callout image generation
> > - Unique construction image background colors for up to four sub-model
> levels.
>
> This is nice!!!
>
> Jaco
|
|
|
In lugnet.cad, Anders Isaksson writes:
> "Jaco van der Molen" <jmolen@zonnet.nl> skrev i meddelandet
> news:HDJ79v.211H@lugnet.com...
> > While rendering a model I got a JPEG error and LPub seems to stop.
> > What is that error and what can I do about it?
>
> Kevin, are you using Delphi? And the jpeg unit from Borland? There is a
> problem with jpeg pictures in the size range 1-2MB if I remember correctly.
> I've seen it talked about in the Delphi newsgroups, but I'm not sure if
> anyone has really found a fix (apart from using some other jpeg library).
Hi Anders,
Yes. I'm using Borland C++ builder 5 and their jpeg unit.
>
> I'd recommend .png instead, if that format is acceptable - the file sizes
> are about the same as .jpg, but the compression is lossless - much better
> pictures.
Do you know of a Delphi compatible PNG package? I'd *love* to use PNG.
Thanks,
Kevin
>
> --
> Anders Isaksson, Sweden
> BlockCAD: http://user.tninet.se/~hbh828t/proglego.htm
> Gallery: http://user.tninet.se/~hbh828t/gallery/index.htm
|
|
|
"Kevin L. Clague" <kevin_clague@yahoo.com> skrev i meddelandet
news:HDLAnL.1482@lugnet.com...
> Do you know of a Delphi compatible PNG package? I'd *love* to use PNG.
I sent the one I have found, and used, to your private mail. I use it with
Delphi 5, so you shouldn't have too much trouble with C++ Builder 5, which
is a bit newer.
--
Anders Isaksson, Sweden
BlockCAD: http://user.tninet.se/~hbh828t/proglego.htm
Gallery: http://user.tninet.se/~hbh828t/gallery/index.htm
|
|
|
In lugnet.cad, Kevin L. Clague writes:
> Do you know of a Delphi compatible PNG package? I'd *love* to use PNG.
I know that Anders already responded to this privately, but I'm posting this
in case his response was different.
The official PNG library (from the creators of the PNG format) has Borland
C++ Builder 5 project files, along with some instructions on how to use the
library from C++ Builder. They probably have binary DLL distributions, but
I personally found it easier to just compile my own static libraries (using
their Visual Studio project files). This allowed me to have PNG support
statically linked into my program, and also allowed me to set the
compile-time options the way I wanted.
You can find the libpng download page here:
http://www.libpng.org/pub/png/libpng.html
One note about libpng. I personally found it to be a royal pain to use.
You'll DEFINITELY need to read the documentation. The library has all kinds
of support for being used to do things like display progressive PNG files
while downloading, but these added features come at the expense of making
simple PNG loading and saving much more difficult than they should be.
If you want you might look at the TCPngImageFormat class in the LDView
source. Feel free to use any of the code there you want, for that matter.
The class is about 350 lines long, and all it does is handle reading and
writing a PNG file into and out of my internal image format. I have another
generic class that handles format-independent image operations.
You can probably even use the classes directly (they at least used to
compile in Linux, so I don't see why Builder would be a big problem). If
you do so, though, you should be aware that their base class implements
reference counting, and their destructors are protected. Because of this,
you need to use their release() member function instead of delete, and
cannot create an instance directly, only via new.
--Travis Cobbs (tcobbs@remove.halibut.com)
|
|
|
Anders and Travis,
Thanks so much for all the help. I can hardly wait to switch to PNG support.
Bitmaps are lossless, but huge, and JPEG is compact but lossy. It will be
great to just use the one format.
Kevin
In lugnet.cad, Travis Cobbs writes:
> In lugnet.cad, Kevin L. Clague writes:
> > Do you know of a Delphi compatible PNG package? I'd *love* to use PNG.
>
> I know that Anders already responded to this privately, but I'm posting this
> in case his response was different.
>
> The official PNG library (from the creators of the PNG format) has Borland
> C++ Builder 5 project files, along with some instructions on how to use the
> library from C++ Builder. They probably have binary DLL distributions, but
> I personally found it easier to just compile my own static libraries (using
> their Visual Studio project files). This allowed me to have PNG support
> statically linked into my program, and also allowed me to set the
> compile-time options the way I wanted.
>
> You can find the libpng download page here:
>
> http://www.libpng.org/pub/png/libpng.html
>
> One note about libpng. I personally found it to be a royal pain to use.
> You'll DEFINITELY need to read the documentation. The library has all kinds
> of support for being used to do things like display progressive PNG files
> while downloading, but these added features come at the expense of making
> simple PNG loading and saving much more difficult than they should be.
>
> If you want you might look at the TCPngImageFormat class in the LDView
> source. Feel free to use any of the code there you want, for that matter.
> The class is about 350 lines long, and all it does is handle reading and
> writing a PNG file into and out of my internal image format. I have another
> generic class that handles format-independent image operations.
>
> You can probably even use the classes directly (they at least used to
> compile in Linux, so I don't see why Builder would be a big problem). If
> you do so, though, you should be aware that their base class implements
> reference counting, and their destructors are protected. Because of this,
> you need to use their release() member function instead of delete, and
> cannot create an instance directly, only via new.
>
> --Travis Cobbs (tcobbs@remove.halibut.com)
|
|
|