Automatically add newly created footprint libraries to the project fp-lib-table

Bug #1465868 reported by Simon Richter on 2015-06-16
26
This bug affects 5 people
Affects Status Importance Assigned to Milestone
KiCad
Wishlist
Unassigned

Bug Description

I find it confusing that after creating a new footprint and saving it to a new library, I still cannot use the footprint because the library is not in the project configuration.

I think this could be done automatically, and it might make sense to have this in the release.

I'm not thrilled with that idea because I often work on footprint
libraries that are not part of a project. I wouldn't be opposed to
asking the user if they want to add the library to the current project.
 Of course you could make the same argument with Eeschema component
libraries as well.

On 6/16/2015 6:27 PM, Simon Richter wrote:
> Public bug reported:
>
> I find it confusing that after creating a new footprint and saving it to
> a new library, I still cannot use the footprint because the library is
> not in the project configuration.
>
> I think this could be done automatically, and it might make sense to
> have this in the release.
>
> ** Affects: kicad
> Importance: Wishlist
> Status: New
>
>
> ** Tags: fp-lib-table fpedit
>

Nick Østergaard (nickoe) wrote :

One might think of not using a popup windows to query the use, but rather use a modified ok button that say "Ok and add to project" or something like that. This is merely a suggestion, I have not yet thought it through completely.

Rene Poeschl (poeschlr) wrote :

I agree with Nick. This is very confusing to a lot of new kicad users. There could simply be a question "would you like to add this to the global or to the project local library table?" (With a hint that the library manager can be used to get more control over the details of how it should be added to the table. Could even have a third button "start library manager".)

I think the case where you do not want the new library added to anything does not happen often.

Seth Hillbrand (sethh) wrote :

Adding symbol libraries does this, we should match the behavior in 6 (or 5.1)

Changed in kicad:
milestone: none → 6.0.0-rc1
Jeff Young (jeyjey) wrote :

Matching the symbol library behaviour was added in 5.1.

Changed in kicad:
status: New → Fix Committed
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers