yorik wrote: ↑Mon Jan 14, 2019 2:54 pm
About library objects being a new py object type, I am not sure...
...
Why are you actually interested in doing that way?
I don't want a new pyobject, only to consider adding FCLib as a valid file type. Really, the idea is to designate the file as containing models / data which is not intended to be complete on it's own, but rather as support for other documents, however it may be used.
So, if I have a file that's an FCLib file, there's absolutely no difference between it and FCStd, it's just a convention that tells me it has models / sketches that I find generally helpful / useful in other projects. It's a library of frequently-used models / data. Nothing more. Really, it suggests that the models contained within aren't intended to serve as anything useful on their own, and really only serve as a supporting library for a production model.
Bentley actually uses that convention for DGN's. There's the DGN file, then DGNLIB files which are DGN's but named differently just to indicate the way the data they contain gets used. It's purely a user-level naming convention and should have zero effect on any other code in FreeCAD.
Probably the parts library is not found... basically 1) it checks the User parameter:Plugins/parts_library/destination parameter for the library path (which is normally set when you run the current parts library macro), and 2) if that setting is not set, it searches the .FreeCAD/Mod directory, where the addons manager install its stuff.
