kicad-developers team mailing list archive

[jp charras <jp.charras@xxxxxxxxxx>]

Le 08/02/2016 16:39, Wayne Stambaugh a écrit :
> I take this back.  I just tested this by launching Pcbnew, opening the
> footprint editor, and adding a new library in the footprint editor then
> launching Eeschema and opening CvPcb to assign footprints and the new
> library was already available in the footprint library table.  The only
> way I see this not working is when Eeschema and Pcbnew are launched as
> separate applications.
> 

The issue is more tricky and very strange:

It happens when cvpcb is run *before* Pcbnew, and when the global fp lib
table is modified:
In this case, the modification (adding or removing a library) of the
global fp lib table made by Pcbnew is not taken in account.
The fp lib table shows the the change, but the actual available
libraries (both in Cvpcb and Pcbnew, for instance when running the fp
lib viewer)are those before the fp lib table.

To reproduce this issue:
Run kicad, then Eeschema then Cvpcb (before running Pcbnew).
Cvpcb and/or Eeschema can be closed.

Now run Pcbnew and change the global fp lib table.
(there is no issue with changes of the project lib table)

The changes are not seen when running Cvpcb, or ModView or Modedit: the
available libraries are the "old" libraries.

If changes are made from Cvpcb, I did not seen this issue.
I do not see issues when:
- Pcbnew is run before Cvpcb.
- Changes are made in Project fp lib table.
- Changes are made from Cvpcb.

Looks like a fp lib cache is not always rebuilt.

-- 
Jean-Pierre CHARRAS