The Embedded Library – What’s it for? How it came to be?
The Embedded Library is designed to store custom, project-specific objects in the project itself (rather than in your file system) to ensure that they are always available and editable. Prior to the debut of the Embedded Library in ARCHICAD 13, objects specific to the given project were stored in a project-specific library somewhere in the file system. This was an additional library besides the usual ARCHICAD and Office Libraries and had to be managed separately, adding another layer of complexity. The Embedded Library is aimed at eliminating the need for a project-specific library in your file system, since with its help all project-specific objects and their needed macros, textures, etc. can be stored in the project file itself. The Embedded libraries may contain:
- Object files you create and save yourself (e.g. Patch, Stair, Trusses, Custom Object, Custom Door/Window components)
- Any object file that you browse for and add to this library, including web objects downloaded through GDL Web Control
- GDL Objects dropped into the ARCHICAD application from either your file system on your computer or from the page of an object on the bimcomponents.com portal.
- MEP objects coming from an imported IFC file.
- Blocks coming from a DWG file and converted into GDL Objects.
- Image files loaded for use as material textures or other purposes.
- Embedded objects of a Hotlinked Module will be included in the Embedded Library of the host project (they will be removed when the Hotlinked Module is removed from the host project)
If you work in teamwork, you must embed objects created by add-ons, like stairs and trusses, otherwise editing these elements will not be possible. It is highly recommended to embed custom objects and custom door/window components. Do not embed library parts form the ARCHICAD library.