this wording “rescue” is a very confusing one, i wish that could be changed one day.
on to the topic.
metadata is not updated.
you will manually need to add same part again from lib, give it the same refdes as the old one,
given that you know which ones has changed and can keep track of that , and being willing to repeat over and over again.
of course its completely unacceptable.
this is actually a very important feature, not lacking in any other e-cad tool i have worked with.
(cadence, orcad / mentor, design capture / dx design )
? if i change a symbol in the lib and don’t rescue it (unselect the tick mark for that symbol in the rescue dialog) -> it is updated in the schematic. (Behavior of a 2 year old nightly. And of 4.0.6 under fedora)
My test documented. After i change the symbol in the lib and save it the rescue dialog opens automatically. (You can also start it from the menu if it does not open)
the text fields you add to the symbol/part ?
footprint being one of the fields
and much more you can add, like manufacturer, tolerance, rating etc etc
i doubt kicad even will notice you have done any changes to them.
so the refresh/reload of symbols should not be a pop-up question from kicad about rescuing, it should be an option in tools or somewhere to refresh design lib so you can do it at will, not when kicad thinks he found something.
In most cases you would not want to have you metadata messed up, just because KiCad finds another version of your symbol.
However, what one could dream about is a tool that would let you search out for instance all capacitors with a value of 100nF and let you update all the different metadata fields for those symbols. (A nice feature could be that it would only update those fields that were edited,leaving the rest alone.) This would make it easier to enter metadata that can be used for BOM creation.
Currently the most efficient strategy to accomplish the same end result is to create “atomic” parts for the most used symbols, so that the information is already there when inserted into the schematic.
Thanks Rene, I had not fully discovered the table editor, I thought it was just for displaying an overview, but discovered now one can update the fields. However I found the edit to be a bit shaky. Sometime it would take a double click, other time not. And if I edit and apply changes to one field the next symbol I click on will also get that value, so may be some more work is needed there (using unsigned Dec. 8 Windows nightly).
I do think see what Nicholas is after though, One has created a schematic, without much metadate or with incorrect ones in it and now you want to use a pre-existing “molecular” part to get that metadata for BOM/ordering info updated instead of retyping it in again.
For my molecular parts, I have symbol names like R_1206_10K_RC1206FR-0710K and with all needed footprint and ordering info defined. On insertion I change the value to 10K. The part will still reference R_1206_10K_RC1206FR-0710K in my custom library, it is just the displayed value that is changed. If I look at its properties all the original info for that part is displayed and ready for use in Pcbnew or creating a BOM.
Some of use like to live dangerously . Actually if there is a time one should go for the nightly that is in the pre-release period after the feature freeze (which is already in effect) to help developers pinpoint as many bugs as possible before the final V5 release.
Some precautions are vise though: frequent backups of everything of course, keeping up to date on what is going on on the bug tracker and the KiCad code list with repect to recent changes (I like this view ), and perhaps above all (that probably applies to any version in use now): Not to rely on referencing the official kicad libraries directly even when stored locally, or at least not at time of conversion to the new sym-lib-table format, as they are being reorganized and one could risk soon obsolete library names to get hard coded into the project files at conversion. And of course the risk might not be worth taking for time critical projects in the final stages. One should not go into this expecting that everything works perfectly.
I usually do this kind of testing with a separate installation in a VM, but right now I have reorganized my custom library and successfully converted all my projects to the new sym-lib-table format for my main installation after the initial testing period in a VM (only relying on two libraries: my own custom library and the official power library). I am really impressed with how responsive the developers are to the bug reports. Also one should not overlook the fact that the nighties have many bugs fixed that have existed for a long time, not only in the later versions.
The reason it would be important for me:
Ensuring integrity. (Has somebody outside the kicad developers tempered with the installer? The package could even be tempered with in transit. Downloading unsigned stuff is a big security risk.) This of course only works if the code signing procedure is itself secure.