Component Chooser: Component Name Clash, Issue: Uniqueness Does Not Include Library Name

Bug #1672300 reported by Andrey Kuznetsov
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
KiCad
New
Undecided
Unassigned

Bug Description

I copied a component from default lib to my private lib, modified pinout and saved it while keeping the original name.
Component chooser shows me my new part, new pinout, so I place it into my escheema sheet, but once I do the pinout is wrong because it took the component with the same name which was in the default library.
Why is library name not part of component uniqueness check? Need to store components with library names, internally so name clashing like this doesn't happen.
People are sure to use the same names at some point and if it's in the default lib then it'll get screwed.

From the very latest nightly, from kicad-r7865.28a6ca1e2-x86_64.exe

Revision history for this message
Chris Pavlina (pavlina-chris) wrote :

This is a flaw inherent in the way KiCad's library system works, and it dates all the way back to the beginning of KiCad. It is going to be changed in the near future, because we're reimplementing the entire library system to work like footprint libraries do.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.