I'm seeking your wise advice on proper file paths (relative or absolute) for the various LDraw tools, and why they don't seem to behave the same between themselves.
In my ldraw folder I have these sub-directories, among others:
p/
parts/
Unofficial/
User/
Unofficial (for uncertified tracker parts) and User (for my own parts) each have their own p/ and parts/ subfolders, so they are both valid ldraw libraries. User also has a number of subfolders for parts authoring projects.
So I'm working on a part in one of those project folders in the User library, and it uses a custom primitive that is also in the User library (obviously in User/p/). To get this primitive to appear in LDPE, I have to give it this path: User\p\48\prim.dat. Some notes:
Now on to LDView. When I open the same part in LDView, the custom primitive isn't found, even though both User and User/p/ are set as extra search paths. To make the prim appear, I have to change the pathname to the full pathname from my disk (so Users/nwperry/ldraw/User/p/48/prim.dat).
Finally, out of curiosity I tried LDCad. In this case, the full pathname didn't work, but it was sufficient to just use 48\prim.dat as you would expect in any part file. User is designated as one of my unofficial libraries in LDCad's settings, and in this case the behavior is as I expect: it finds the primitive in the p folder in that library.
So the question is, could I do something differently so that all these programs will find the custom primitive, without having to have a different version of the part file for each different tool?
And are all these programs behaving as expected? It seems odd that I have an unofficial primitive in an unofficial library, but the programs don't find it there even though I've specifically set them up to do so.
In my ldraw folder I have these sub-directories, among others:
p/
parts/
Unofficial/
User/
Unofficial (for uncertified tracker parts) and User (for my own parts) each have their own p/ and parts/ subfolders, so they are both valid ldraw libraries. User also has a number of subfolders for parts authoring projects.
So I'm working on a part in one of those project folders in the User library, and it uses a custom primitive that is also in the User library (obviously in User/p/). To get this primitive to appear in LDPE, I have to give it this path: User\p\48\prim.dat. Some notes:
- User is set at the "parts authoring" folder in LDPE, and Unofficial is set as the "Unofficial" folder (even though they're both unofficial libraries).
- LDPE creates its own "ldparteditor-temp-project" folder, which I'm not using (never found the reason to). It's located outside my ldraw folder.
- I've used relative paths in LDPE before, but for some reason ..\p\48\prim.dat doesn't work.
Now on to LDView. When I open the same part in LDView, the custom primitive isn't found, even though both User and User/p/ are set as extra search paths. To make the prim appear, I have to change the pathname to the full pathname from my disk (so Users/nwperry/ldraw/User/p/48/prim.dat).
Finally, out of curiosity I tried LDCad. In this case, the full pathname didn't work, but it was sufficient to just use 48\prim.dat as you would expect in any part file. User is designated as one of my unofficial libraries in LDCad's settings, and in this case the behavior is as I expect: it finds the primitive in the p folder in that library.
So the question is, could I do something differently so that all these programs will find the custom primitive, without having to have a different version of the part file for each different tool?
And are all these programs behaving as expected? It seems odd that I have an unofficial primitive in an unofficial library, but the programs don't find it there even though I've specifically set them up to do so.
, Beta 2 will warn about that and remove the offending location from the list.
