|
|
 | | Re: LSynth 2.0 Available
|
| (...) Installers are highly uninspiring, but I will fix this for the next release (which will happen as soon as I fix and test the installer.) Kevin (22 years ago, 17-Jan-03, to lugnet.cad, lugnet.cad.dev, lugnet.inst)
| | | | | Re: LSynth 2.0 Available
|
| I really like your tool, it will save me a lot of time and struggling and allow mw to add to my models I do, hower have a a comment on the installer you use, it sucks.. instead of placing the parts in the correct parts directories it placed them in (...) (22 years ago, 17-Jan-03, to lugnet.cad, lugnet.cad.dev, lugnet.inst)
| | | | | Re: Seeking input on reused user parts in building instructions
|
| "Kevin Clague" <kevin_clague@yahoo.com> wrote in message news:H8t9F9.BAt@lugnet.com... (...) parts (...) in (...) was (...) Yeah! I have seen this with many of the train models I have created. In one case I used a sub-model 8 times and LPub (...) (22 years ago, 17-Jan-03, to lugnet.cad.dev, lugnet.inst)
| | | | | Re: LSynth 2.0 Available
|
| Hi Ahui, If you are still having problems, just email an example that does not work, or post it here. I will figure it out and get back to you. Kevin (...) (22 years ago, 17-Jan-03, to lugnet.cad, lugnet.cad.dev, lugnet.inst)
| | | | | Re: LSynth 2.0 Available
|
| Hi Dave, Right now the installer is too simple. It needs to know where the LDraw directory is, so it can add some parts to your parts directory. It does a simple search for this: LDRAW\MKLIST.EXE on your hard disks. It cannot find it. I'd guess one (...) (22 years ago, 17-Jan-03, to lugnet.cad, lugnet.cad.dev, lugnet.inst)
| | | | | Re: LSynth 2.0 Available
|
| Bill, My initial thought is.... what are the chances that someone will find a commercial use for this program? But in thinking about it more, I have no idea how far other contributing authors will take this program, so out of respect for their (...) (22 years ago, 17-Jan-03, to lugnet.cad, lugnet.cad.dev, lugnet.inst)
| | | | | Re: LSynth 2.0 Available
|
| (...) GPL is the best in terms or preserving the author's rights. Public Domain is a bad idea - it means you surrender any rights to the software, and people can then basically use it to build their own commercial programs and wouldn't owe you (...) (22 years ago, 16-Jan-03, to lugnet.cad, lugnet.cad.dev, lugnet.inst)
| | | | | Re: Seeking input on reused user parts in building instructions
|
| Hi Will, As I was writing the original post, I realized that I had a question for myself, does the X4 go on the image itself, or does it go in the web pages generated by LPub. If I make it go into the web pages, then I think it leaves more (...) (22 years ago, 16-Jan-03, to lugnet.cad.dev, lugnet.inst)
| | | | | Re: Seeking input on reused user parts in building instructions
|
| (...) (22 years ago, 16-Jan-03, to lugnet.cad.dev, lugnet.inst)
| | | | | Re: Seeking input on reused user parts in building instructions
|
| While it is a great idea to supress the multiple rendering of the same steps, I'm not sure there is really any added value to displaying the "x4" on the last step. I find that I always take a pass through the final rendered instruction images, in my (...) (22 years ago, 16-Jan-03, to lugnet.cad.dev, lugnet.inst)
| | | | | Seeking input on reused user parts in building instructions
|
| Hi, I've decided to tackle an issue that has been on my mind for a while. LPub's handling of building instructions, where sub-model user-defined parts are used multiple times in the overall design. It all started when I was editing a DSDK model (...) (22 years ago, 16-Jan-03, to lugnet.cad.dev, lugnet.inst)
| | | | | * LDrawDesignPad LDDP 1.4 released *
|
| Hello! New version is out now. Get it at (URL) ! + = New feature * = Bugfix - = Removed feature Changes since version 1.3 v1.4 01/16/2002 * Fixed some L3P problems with long filenames or -paths * Fixed list of recently used files * Fixed a problem (...) (22 years ago, 16-Jan-03, to lugnet.announce, lugnet.cad, lugnet.cad.dev) !
| | | | | Re: LSynth 2.0 Available
|
| Tim and Michael, I'd love to see this feature as well, although it is easy to say from the outside. We have no idea how MLCAD is orgranized, so this may be pretty hard to do, especially getting nice preview images of synthesized parts. Kevin (...) (22 years ago, 15-Jan-03, to lugnet.cad, lugnet.cad.dev, lugnet.inst)
| | | | | Re: LSynth 2.0 Available
|
| (...) an (...) the (...) so (...) Right. Keep up the good work! I am looking forward to the next version. Jaco (22 years ago, 15-Jan-03, to lugnet.cad, lugnet.cad.dev, lugnet.inst)
| | | | | Re: LSynth 2.0 Available
|
| (...) Great! They are 73590A and B btw... :-) Jaco (22 years ago, 15-Jan-03, to lugnet.cad, lugnet.cad.dev, lugnet.inst)
| | | | | Re: LSynth 2.0 Available
|
| (...) Not really. I tend to waver somewhere between the GPL and Public Domain, depending on how long it's been since I've had trouble with piece of closed software. Of the few licences here (URL) I've read, the zlib license is the shortest, and I do (...) (22 years ago, 15-Jan-03, to lugnet.cad, lugnet.cad.dev, lugnet.inst)
| | | | | Re: LSynth 2.0 Available
|
| Hi Ahui, You do not need to use an editor to add these coments. Lsynth compensates for MLCAD's WRITE statements, by ignoring the WRITE keywoard. Two things to examine: 1. LSynth is case sensitive, so SYNTH is not the same as synth. 2. If you are (...) (22 years ago, 15-Jan-03, to lugnet.cad, lugnet.cad.dev, lugnet.inst)
| | | | | Re: LSynth 2.0 Available
|
| Has anyone besides Kevin been able to get LSynth to work? I can get it to run the examples.mpd file but when ever I get my own file it does nothing? I have added the comments in a text editor (since MLCAD adds the WRITE statements to commets) and (...) (22 years ago, 15-Jan-03, to lugnet.cad, lugnet.cad.dev, lugnet.inst)
| | | | | Re: LSynth 2.0 Available
|
| Hi Don, I have no idea what license to choose. Do you have a recommendation? Kevin (...) <snip> (22 years ago, 15-Jan-03, to lugnet.cad, lugnet.cad.dev, lugnet.inst)
| | | | | Re: LSynth 2.0 Available
|
| (...) Sure, send it along. I think the only sticky point that should be resolved before creating the project is the source code license. (I say "sticky" because we seem to have gotten stuck there with the parts library and a recent attempt to get (...) (22 years ago, 15-Jan-03, to lugnet.cad, lugnet.cad.dev, lugnet.inst)
|
|
