Good time of day!
What fun it was! :)
I have updated the components from the library on the schematic.
After that, all the components that were mirrored vertically or horizontally lost it. Incredibly!
When updating the PCB from the schematic everything went wrong .
The tracks were renamed, and it was not enough to simply turn the component on the PCB.
I had to look for these components on the schematic, mirror them again manually.
It was a fun job, especially for resistors and capacitors! :)
If you placed the component has been changes, updated the components from the library will get the latest version to update the schemtiac component version
you can try
for this issue, this component must have been updated at Library, when you update, it updates the schematic version, the preview window is for checking these changes
Starting with v6.4.20.8, the editor enables the historical versioning
mechanism for schematic and footprint libraries. When a symbol or
footprint library is saved, a new history record will be generated each
time it is saved, and when the library is placed on the canvas, the
latest historical version of the library will be used. For example,
MAX232 schematic library and footprint SOP-8, when the MAX232 schematic
library is bound with SOP-8, it is placed in the schematic diagram and
converted to PCB. At this time, the version used by the SOP-8 of the PCB
is the historical version that was placed in the schematic diagram at
that time. , if you edit the footprint library SOP-8 again and add one
more pad, the schematic diagram will be transferred to a new PCB again,
and the original footprint will still be used. If you want to use the
new version footprint, updates the corresponding component at schematic
design menu. This design ensures that the version used at the time is
not affected by subsequent footprint modifications, ensuring that the
version placed at that time is always used. If it is a schematic diagram
drawn before v6.4.20.8, the latest version of the footprint will still
be taken directly when transferring or updating the PCB, because the old
file placement device does not record the historical version at that
time. This mechanism does not currently support private deployment
versions.