schema: new lib system, components marked as unknown stays unkown

Bug #1733906 reported by Nicholas Savenlid
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
KiCad
Fix Released
Undecided
Unassigned

Bug Description

With this new lib handling, one problem arose

If you open a schematic/project where you happens to be missing a lib, all those components missing a lib gets marked with a "??"

this has always been that way so nothing new, and not a problem either.

But now it wont help to include the missing lib.

Components will stay "??" even after that component now is included within one of your libs.

Now you need toreplace that component again from the lib with the exact same component.

This was not the case before and creates a lot of extra work.

Revision history for this message
Wayne Stambaugh (stambaughw) wrote : Re: [Bug 1733906] [NEW] schema: new lib system, components marked as unknown stays unkown

There is nothing that can be done about this. Once the remapping is
done, any symbols that cannot be mapped do not have a library nickname
assigned to them. There is no way for the remapping algorithm to guess
any future library nicknames when a symbol cannot be remapped. I could
allow remapping for partially mapped schematics but this could be
dangerous and would make some fairly complex code even more complex.
I'm not sure how to move forward on this one but I'm open to suggestion.

On 11/22/2017 11:31 AM, Nicholas Savenlid wrote:
> Public bug reported:
>
> With this new lib handling, one problem arose
>
> If you open a schematic/project where you happens to be missing a lib,
> all those components missing a lib gets marked with a "??"
>
>
> this has always been that way so nothing new, and not a problem either.
>
> But now it wont help to include the missing lib.
>
> Components will stay "??" even after that component now is included
> within one of your libs.
>
> Now you need toreplace that component again from the lib with the exact
> same component.
>
> This was not the case before and creates a lot of extra work.
>
> ** Affects: kicad
> Importance: Undecided
> Status: New
>

Revision history for this message
jean-pierre charras (jp-charras) wrote :

Hi Wayne,

It could be a job for the new Component to Symbols Links Editor.
Just propose a LIB_ID to "Orphan" components, based on the nmae of the symbol.
The user will have to validate by hand the proposed choice.

Revision history for this message
Nicholas Savenlid (nicholas-z) wrote :

After remapping to the new scheme you get results about what is missing.

But I do not thinks the remapping is reversible at that point, should you find some warnings/erros.

Could a dry run be a possibility ?

get the warnings/errors beforehand

Also it could be could to show only warnings/errors as default not to miss the warnings in the info/action stream.

Revision history for this message
Wayne Stambaugh (stambaughw) wrote : Re: [Bug 1733906] Re: schema: new lib system, components marked as unknown stays unkown

Hey JP,

This is one option. The other option is to allow remapping the
schematic any time there are any LIB_IDs that do not have an assigned
library nickname. I could add an option to keep existing mapping and
only remap the broken links. I'm fine with either option. I haven't
tried you symbol link editor so I'm not familiar with it.

Cheers,

Wayne

On 11/22/2017 12:16 PM, jean-pierre charras wrote:
> Hi Wayne,
>
> It could be a job for the new Component to Symbols Links Editor.
> Just propose a LIB_ID to "Orphan" components, based on the nmae of the symbol.
> The user will have to validate by hand the proposed choice.
>

Revision history for this message
Wayne Stambaugh (stambaughw) wrote :

I'm OK with adding a dry run checkbox to the remapping dialog that only shows the changes that would be made so users can back out and fix any broken libraries.

Revision history for this message
Nicholas Savenlid (nicholas-z) wrote :

thanks

it will give a good enough fix until something better pop up.

Revision history for this message
Jeff Young (jeyjey) wrote :

Is this something we want to address for 5.0.0-rc2?

Revision history for this message
Wayne Stambaugh (stambaughw) wrote :

I think JP's "Edit Symbol Library Links..." tool addresses this issue adequately. The library specifier must be included to insure you have the correct symbol. This is a requirement for the new schematic symbol definition so that is not going to change. Once the new schematic file format is written, this issue will go away because the symbols will be embedded in the schematic file instead of linked to the library symbol.

Revision history for this message
Nicholas Savenlid (nicholas-z) wrote :

i can chime in and say that after this "map orphans" button came in, all my problems are gone

i just clean up the link errors and auto-remap

so i dont suffer anything anymore in this respect

also the possibility refresh the fields of the symbols is just wonderful

its really getting a professional grade feeling kicad

Revision history for this message
Jeff Young (jeyjey) wrote :

Excellent. Thanks guys.

Changed in kicad:
status: New → Fix Committed
Changed in kicad:
status: Fix Committed → Fix Released
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.