LDraw.org Discussion Forums
[LDCad] Part Snapping missing/errors - Printable Version

+- LDraw.org Discussion Forums (https://forums.ldraw.org)
+-- Forum: LDraw Programs (https://forums.ldraw.org/forum-7.html)
+--- Forum: LDraw Editors and Viewers (https://forums.ldraw.org/forum-11.html)
+--- Thread: [LDCad] Part Snapping missing/errors (/thread-23807.html)

Pages: 1 2 3 4 5 6 7 8 9


RE: Part Snapping missing/errors - Philippe Hurbain - 2020-07-18

Relatively recent yes, when I created the animal "segment" patterns (such as https://www.ldraw.org/parts/official-part-lookup.html?folder=parts&partid=31111p02). There was already a patterned version, but it was not subparted (https://www.ldraw.org/parts/official-part-lookup.html?folder=parts&partid=31111p01)


RE: Part Snapping missing/errors - Roland Melkert - 2020-08-04

I've processed up to message #48

And I also added a new bunch of files by Alex Taylor (incl some unofficial ones)

As always the latest (test) shadow is at:
http://www.melkert.net/action/download/shadow.sf


RE: Part Snapping missing/errors - N. W. Perry - 2020-08-05

The venerable Fabuland shovel (4330) need snaps on its handle and shaft. (And is the actual part really that long??!)


RE: Part Snapping missing/errors - N. W. Perry - 2020-08-05

(2020-08-04, 20:42)Roland Melkert Wrote: I've processed up to message #48

And I also added a new bunch of files by Alex Taylor (incl some unofficial ones)

As always the latest (test) shadow is at:
http://www.melkert.net/action/download/shadow.sf

I'm a little unclear how the shadow.sf file in the seeds directory relates to the shadow libraries in Application Data. How do the newly added parts get into the official library, and what if I'm using a custom library, containing all the official content but also whatever new files I've added?

Just want to be sure I'm not updating the hard way. :-)


RE: Part Snapping missing/errors - Roland Melkert - 2020-08-06

(2020-08-05, 23:06)N. W. Perry Wrote: I'm a little unclear how the shadow.sf file in the seeds directory relates to the shadow libraries in Application Data. How do the newly added parts get into the official library, and what if I'm using a custom library, containing all the official content but also whatever new files I've added?

The contents of .sf (plain zip) files are synchronized with the per user location at program start.

This way each user can setup their own bins and options etc, while still having defaults out of the box.

It will only update existing files and remove obsolete ones, if you got additional custom content that will not change.

If you are using an unpacked shadow it shouldn't affect you at all, unless you unpack the updated shadow (.csl) in the user location again.


RE: Part Snapping missing/errors - N. W. Perry - 2020-08-07

(2020-08-06, 20:20)Roland Melkert Wrote: The contents of .sf (plain zip) files are synchronized with the per user location at program start.

This way each user can setup their own bins and options etc, while still having defaults out of the box.

It will only update existing files and remove obsolete ones, if you got additional custom content that will not change.

If you are using an unpacked shadow it shouldn't affect you at all, unless you unpack the updated shadow (.csl) in the user location again.

What I've been doing is copy the offLib.csl to my own custLib.csl, then I unpack that and use it as my shadow library so I can save corrections and new shadow files.


So if I understand correctly, my process should be:

  • -Before installing the new .sf, I should re-pack my custom library to custLib.csl
  • -Set custLib.csl as my library so that it will synchronize
  • -Install the new .sf and re-launch LDCad
  • -Re-unpack custLib and switch to that directory when I want to make more changes
I should now have all updated files, plus whatever new ones I'd made (unless they were corrections to existing files, which are now replaced with your updates). Right?


RE: Part Snapping missing/errors - Orion Pobursky - 2020-08-07

(2020-08-07, 0:30)N. W. Perry Wrote: What I've been doing is copy the offLib.csl to my own custLib.csl, then I unpack that and use it as my shadow library so I can save corrections and new shadow files.


So if I understand correctly, my process should be:

  • -Before installing the new .sf, I should re-pack my custom library to custLib.csl
  • -Set custLib.csl as my library so that it will synchronize
  • -Install the new .sf and re-launch LDCad
  • -Re-unpack custLib and switch to that directory when I want to make more changes
I should now have all updated files, plus whatever new ones I'd made (unless they were corrections to existing files, which are now replaced with your updates). Right?

No. You'll destroy your customizations if you do that. You have have more that one shadow library. Better to have a separate shadow library that only contains your altered/added files much like is done with unofficlal parts. Then your custom lib will override the "official" Roland supplied one.


RE: Part Snapping missing/errors - N. W. Perry - 2020-08-07

(2020-08-07, 0:55)Orion Pobursky Wrote: No. You'll destroy your customizations if you do that. You have have more that one shadow library. Better to have a separate shadow library that only contains your altered/added files much like is done with unofficlal parts. Then your custom lib will override the "official" Roland supplied one.

But I actually want the Roland-file to override mine, that's OK. I only want to keep any of my additional files that haven't made it into the "official" package yet. It sounded like those wouldn't get overwritten.

For unofficial parts it's no problem; the shadow info can even be baked into the main file. For official parts, you can only choose one shadow library per search path, but I suppose I can duplicate the official search path (same main folder, but different shadow libs). Keep the offLib as a zipped library, and use an unpacked one for saving my own additions/corrections. Would that work?


RE: Part Snapping missing/errors - Roland Melkert - 2020-08-07

(2020-08-07, 2:52)N. W. Perry Wrote: But I actually want the Roland-file to override mine, that's OK. I only want to keep any of my additional files that haven't made it into the "official" package yet. It sounded like those wouldn't get overwritten.

For unofficial parts it's no problem; the shadow info can even be baked into the main file. For official parts, you can only choose one shadow library per search path, but I suppose I can duplicate the official search path (same main folder, but different shadow libs). Keep the offLib as a zipped library, and use an unpacked one for saving my own additions/corrections. Would that work?

The .sf will sync offLibShadow.csl as a whole.

So you'll need to unpack it (again) yourself. I sugest first renaming the original unpacked folder so you can visualize changes with e.g. winmerge.

Each search location has only one shadow as the content will be appended to the pure part files before parsing start.


RE: Part Snapping missing/errors - N. W. Perry - 2020-08-07

(2020-08-07, 17:19)Roland Melkert Wrote: The .sf will sync offLibShadow.csl as a whole.

So you'll need to unpack it (again) yourself. I sugest first renaming the original unpacked folder so you can visualize changes with e.g. winmerge.

Each search location has only one shadow as the content will be appended to the pure part files before parsing start.

Got it. So I'm already doing it correctly (re-naming and re-unpacking the synced official library). The difficulty is just that MacOS doesn't have a convenient way to merge folders if they contain sub-folders, so I have to do that part manually.