Actions
Forum Thread Details
  • State Verified Answer
  • Locked Locked
  • Replies 4 replies
  • Subscribers 86 subscribers
  • Views 474 views
  • Users 0 members are here
Related
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

How do I find which library a schematic component belongs to?

jaza_tom

I have a schematic.

 

I want to know which library a specific component in the schematic belongs to.

 

How do I do that?

 

Here is the schematic component dialog window I have:

 

image

 

I do see the "Library" text (string) property. Is this all?  Is there no link to be able to edit the library component?

  • 0

    You can view the library easily by activating the SCH Inspector panel using View | Inspector. Clicking on a symbol will bring up lots of useful information including the "Library" field.

    image

  • 0 in reply to e14softwareuk

    OK thanks,

     

    But what if I have two libraries with the same name?  For example, if I have one library that is saved within a project, and another library that is installed as a global environment library, and they have the same name, how do I know which library the part is actually from?

     

    Also, does the concept of a part "belonging to a library" even a thing in CircuitStudio?  For example, if I update the pcb footprint for a part in a library, it does not automatically update the PCB layout for that component in my project right?  In other words, the second you place an object, the link the library it came from is broken, right?

  • 0 in reply to jaza_tom

    Once a part is loaded onto the schematic from a library file the data is copied. I understand what you are saying with regards to "if I update the library..." but think of it this way - if you have a completed design you would not want it to randomly change if someone happened to edit a library you are using. From a library you can push changes through to the design files in a controlled manner.

     

    It would not be considered good practice to have more than one library with the same name, that would create confusion not just within the product but when managing the files at a file system level.

  • 0 in reply to e14softwareuk

    This makes a lot of sense.  Thanks Peter!