LDCad 1.6c (win+linux)


LDCad 1.6c (win+linux)
#1
I decided to release LDCad 1.6c early  Big Grin

I was planning on some more scripting examples and maybe a new animation but unfortunately I can't seem to find the time needed at the moment.

Also the 1.6c version has been long overdue

This version includes mostly (minor) bug fixes and some tweaks to existing behavior.

It also includes some new stuff, namely:
  • File cleanup templates
  • Part bin export
  • Scripting api extensions (I also decided to open up the lua 'io' module.
  • Some new scripted macros including some MLCad 'HIDE' tools.
  • New, 1802, templates, also tweaks some existing ones to be more consistent with their static counter parts.
  • Snap and mirror info for, most of, the 1802 library.
For the full list of changes see the changeLog.txt file.

I was also planning on overhauling the part bin structure, but decided to leave that for 2.0 instead.


You can download the newest version here:
http://www.melkert.net/LDCad/download
Reply
RE: LDCad 1.6c (win+linux)
#2
(2019-06-26, 20:17)Roland Melkert Wrote: I decided to release LDCad 1.6c early  Big Grin
Yeah !!!

Quote:
  • Part bin export
What's the intended purpose?
Reply
RE: LDCad 1.6c (win+linux)
#4
(2019-06-27, 5:53)Philippe Hurbain Wrote: What's the intended purpose?
People asked for a way to export part lists.
Reply
RE: LDCad 1.6c (win+linux)
#3
(2019-06-26, 20:17)Roland Melkert Wrote: I was also planning on overhauling the part bin structure, but decided to leave that for 2.0 instead.

Hi Roland,

Thanks for this update. I got 1.6c running smoothly.

I did some re-work on the part bins for my self in 1.6b and got most things like I wanted it there.
However, I cannot seem to repeat this entirely in 1.6c.

For example: I'd like the Plate 1x1 with sockets, joints and balls in a modified plate category I created, so that the normal plates category is not too crowded.
[Image: 6043639] [Image: 6039482] [Image: 6043656] [Image: 6039479] [Image: 6123814]
I wanted these to be excluded from the hinges bin.
The strange thing is that I only am able to include the last two in my bin.
The other 3 with sockets and socket and ball are no where to be found.

Any idea how to do that?
Jaco van der Molen
lpub.binarybricks.nl
Reply
RE: LDCad 1.6c (win+linux)
#5
(2019-06-27, 9:58)Jaco van der Molen Wrote: The other 3 with sockets and socket and ball are no where to be found.
Those are in the hinge plate group. I thought I moved all the ball plates there too, but this seems to have fallen trough the cracks.

But if you defined a custom group it doesn't really matter if they are visible somewhere else too, group content doesn't need to be unique.
Reply
RE: LDCad 1.6c (win+linux)
#6
(2019-06-27, 19:19)Roland Melkert Wrote: Those are in the hinge plate group. I thought I moved all the ball plates there too, but this seems to have fallen trough the cracks.

That is the problem: they are not there, due to my own tweaking... :-(

(2019-06-27, 19:19)Roland Melkert Wrote: But if you defined a custom group it doesn't really matter if they are visible somewhere else too, group content doesn't need to be unique.

The thing is, I cannot seem to get them in any group.

I think I messed up my PBG files too much and I must restore them somehow.
Can I just delete the partBin folder to regenerate it?
Jaco van der Molen
lpub.binarybricks.nl
Reply
RE: LDCad 1.6c (win+linux)
#7
(2019-06-27, 19:19)Roland Melkert Wrote: Those are in the hinge plate group. I thought I moved all the ball plates there too, but this seems to have fallen trough the cracks.

I think I now see and understand why: 14418 has 0 !CATEGORY Hinge in it. Just like 14419 and 14704.
Whereas 14417 and 22890 do not have this category meta.

Do we think the category hinge needs to be added to 14417 and 22890?
Jaco van der Molen
lpub.binarybricks.nl
Reply
RE: LDCad 1.6c (win+linux)
#8
(2019-06-28, 7:41)Jaco van der Molen Wrote: I think I now see and understand why: 14418 has 0 !CATEGORY Hinge in it. Just like 14419 and 14704.
Whereas 14417 and 22890 do not have this category meta.

You can force them into any group using

Code:
static partName 14418.dat,14419.dat,14704.dat

at the beginning of the rules.
Reply
« Next Oldest | Next Newest »



Forum Jump:


Users browsing this thread: 1 Guest(s)