Components and Library Search Precedence

When you place a new component in a design, Twin Builder searches in the current project for a definition with the corresponding name. If an appropriate definition exists in the project, that definition is used to satisfy the placement regardless of whether additional instances, even more recent ones, exist in external libraries.

If Twin Builder cannot locate the required definitions in the project, it searches in personal (PersonalLib), user (userlib), and system (syslib) library files, in that order. Once a definition of the correct name is located, the search ends, and that definition is used to satisfy the placement request.

Note:

Once a definition is used, it is transferred to the current project, and remains in the project unless you remove it. See Removing Definitions from a Project for details. To see the definitions included in a project, expand its Definition folders and subfolders in the Project tree.
Modifying component and dependency definitions in libraries, or installing libraries with modified component and dependency definitions, does not update those definitions in projects that contain them. To update project definitions from library definitions, see Updating Project Definitions from Library Definitions.