Pins set and rendered as NC in library editor are not rendered as such once imported in eeschema

I do not have this issue. Please update your Kicad version.

Bonjour Jean-Pierre,

Merci pour votre réponse rapide, mais je ne suis pas certain qu'il s'agisse d'un problème lié à la version de KiCad.

My KiCad version is up-to-date: an own build from the source code bzr 6188 (official 2015 stable release 4.0). My operating system is CentOS 7. I sticked rigorously to the installation instructions either for Kicad or for the component library (both retrieved via bazaar). All builds processed flawessly.

I compiled against wxWidget library which is provided by epel repository (https://fedoraproject.org/wiki/EPEL). Since the combination of KiCad + wxWidget3 + GTK3 is broken (https://bugzilla.redhat.com/show_bug.cgi?id=1228254) I've had to use a gtk-2 compatible flavor of the wxWidget library.

My testing is the following (maybe is it lacking sthg)

-Edit TRANSFO2 from device component lib.
-Mark pin 6 as NC. In the lib editor the pin refreshes itself accordingly with a x.
-Export the edited symbol to let say transfo_nc.lib
-Import transfo_nc.lib in eeschema
-Place the component it contains in the working sheet.
Pin 6 reappears as marked as a circle o

Regards,
Pierre

Jean-Pierre,

I made the following two tests (a with / without component deep copy)

1- Test without component deep copy

  - Edit TRANSFO2 from device component lib.
  - Mark pin 6 as NC. In the lib editor the pin refreshes itself accordingly with a cross x.
  - Export the edited symbol to let say transfo_nc.lib
  - Import transfo_nc.lib in eeschema
  - Place the component it contains in the working sheet.
    Pin 6 reappears as marked with a circle o

2- Test with component deep copy

  - Edit TRANSFO2 from device component lib.
  - Create a new component from the current one (<b>component deep copy </b>)
  - Mark pin 6 as NC. In the lib editor the pin refreshes itself accordingly with a cross x.
  - Export the component in let say transfo_nc_wc.lib
  - Import transfo_nc.lib in eeschema
  - Place the component it contains in the working sheet.
    Pin 6 reappears as marked with a cross x OK

The tests seem to show that the export function does not make a deep copy of the edited
component object. What is also quite disturbing is that the two edited components (shallow or deep copied) appear identical when accessing them in the component library browser but not once
imported in a schematics.

Is this a bug ?

Regards,
Pierre

Avoid to use the same name for 2 different components.
Otherwise, you'll have to manage library priority.

Currently, in "Test without component deep copy" you have 2 different components with the the same name in loaded libraries.

Just change one name, or remove the unwanted component.

PS: the stable release is not yet out. This is a release candidate RC1 (4.0.RC1, not 4.0).