gkmethy wrote:
This is really simple to do in ArchiCAD 14:
In the library manager there is a button for "embed placed objects from selected library". This will embed all the used objects (along with their macros) - and get rid of the linked library.
After this, you can choose to export those embedded objects to a linked library, if you will. Or you can keep them embedded - If you select an object in the embedded library, (in the library manager) the library manager will tell you how many instances are placed in the project. Therefore you can remove objects that you no longer use too.
Read this article:
http://archicadwiki.com/LibraryMigration
Hey Greg
Thanks for correcting me. I was going by memory and got the order wrong. That will teach me for posting before my morning coffee. I should have written embed>export>re-embed. And I do like to export out and re-embed manually, purely because I don't like subfolders in my embedded library. I should mention that, even though it's not a necessary step.
The Library Manager does not show macros, textures, property objects, and UI images as placed - correct? Deleting those as suggested could cause confusion when parts stop working or appearing correctly, no? I presume that's why they embed to folders called 'Object parts (do not modify)' and' Textures, zone stamps and property objects'.
I wish instead that non-placeable parts were shown in italic, much like the 'embedded' attributes display in the Attribute Manager. This way it would be easier to know what to leave the hell alone.
Better still is if all
used
textures, zone stamps, property objects, macros and ui images (did I miss any?) were included automatically (eliminating the Embed Library Parts dialog shown below) and remained hidden in the Library Manager.
It's mentioned in your article and elsewhere that linking libraries reduces file size and saves loading time. I can see how it may bloat your file a
little
(ie. under 5% of the project size), but surely it's more manageable than linking libraries from all over the network? Is the loading time really affected if it's embedded or linked - they both have to come down the line right? And are linked libraries accessible to users who join remotely (I have never tried)?
Apart from embedded library parts appearing as duplicates in multiple hotlinks, I haven't seen any significant hit in terms of performance or methodology in using embedded libraries & server libraries only.
And unless I am imagining things, embedded parts are better to use because if they are copy/pasted into another project (that doesn't currently have that part loaded) it will automatically become embedded in that project, textures, macros, ui images, et al, all automatically included!!! That can't be said for linked or even server libraries!(?)
I'm obviously quite interested in this topic and your response.
Cheers,
Link.