Eeschema R component conflict btw device.lib and device-gost.lib

Bug #1571193 reported by Norman Wood
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
KiCad
Invalid
Undecided
Unassigned

Bug Description

Placing R component from device-gost.lib automatically substituted by R component from original device.lib
Works properly after removing device.lib from list of libraries.

Kicad-win64 4.0.2
latest device-gost.lib from https://github.com/KiCad-RUS/kicad-gost-library

Revision history for this message
Eldar Khayrullin (eldar) wrote :

Hello.
This is place for bugs related with official KiCad bugs.
KiCad-RUS repo maintained from github. Report your bugs in there.

Revision history for this message
Eldar Khayrullin (eldar) wrote :

If you use two libs at the same time Move up a preferred lib or delete original lib from Library Table

Changed in kicad:
status: New → Won't Fix
status: Won't Fix → Invalid
Revision history for this message
Novak Tamas (novak-7) wrote :

@Norman Wood
You probably have two components with the same name in two different libs. This is not supported by KiCad: if you want to create a new component with a name which already exists in another lib, you gonna get an error message. But if you add a whole component library (eeschema - preferences - component libraries - add) which contains colliding names, there is NO checking for duplicate names, so system CAN contain multiple components with the same name.
As .sch file contains only lib search order, then the names of the components (without the lib name), you must avoid duplicate names.

@eldar, should you change status to confirmed, and importance to medium. The component name checking code part, which runs when creating a new component should run on each component in the lib to be added.

Revision history for this message
Novak Tamas (novak-7) wrote :

Addition:
Having two components with the same name is partially supported:
 some parts of the code can handle the duplicates, some parts can't.

- you are not allowed to create duplicate name components (creating the second instance is refused)

- if you add a lib with duplicated names, it is resulting duplicates, as there is no checking for same-name-components when adding the new lib.

- when you "Place component" (and anyhow there are duplicates in libs) you will have a nice list of different components of the same name to pick the appropriate. Their different symbol will be displayed properly for each libs on the picking list.

- if you pick one, not the chosen component will be displayed, but the first hit in search lib order!!
  Even your previously placed and normally displayed components will be changed to new outlook!!

so it's a real mess...
as the only way to this confusing situation is adding a lib with duplicate names, adding a new lib should contain cheking against duplicate names

Revision history for this message
Eldar Khayrullin (eldar) wrote :
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.