One way to go here is to add another check in the DRC:
X Is the schematic design in sync with the libraries?
giving you a list of symbols (may be empty) that isn't in sync.
Then I could by my self decide if I should upgrade some or all symbols that
gives a warning or not.
Magnus
--- In tinycad@..., "Don Lucas" <Don.Lucas@...> wrote:
>
> Phil -
>
> I don't see how this particular example can be considered to be a bug. You
are describing normal and desireable behavior. Just because a symbol is edited
in the library, you don't necessarily want to automatically update all of the
instances of the older version of the symbol. I would be much more concerned if
after updating all instances of older definitions of the symbol, the now unused
definitions stuck around in the design file with no actual instances being used.
>
> Perhaps we could flag older versions somehow so that it was more obvious that
one or more had not been updated, but that is about as far as I would go.
Another user suggested that we add the ability from the symbol editor to push
the newer version of the symbol out to all instances in any open designs - I
would find that a very desireable ability also - but only upon a manual command.
Otherwise, you could risk losing important design info if all symbols were
always automatically updated, potentially also causing symbols to become
disconnected if origins or pin lengths were changed.
>
> Am I missing something here?
>
> Don
>
>
> --- In tinycad@..., "a10d0n" <philipw@> wrote:
> >
> > It is easy to create this situation in v2.60.01.
> >
> > If you enter a symbol from a library on to a schematic then go into the
library/symbol editor and change it (say a pin position) you can then place it
again on the schematic. As the two symbols are not identical there will be two
entries in the database with the same name but different <SYMBOLDEF id='??'>
entries.
> > eg:
> > <SYMBOLDEF id='1'><NAME type='0'>Fred</NAME> {--Definition text--}
> > <SYMBOLDEF id='2'><NAME type='0'>Fred</NAME> {--definition Text--}
> > (I only reversed the orientation of a pin.)
> > This sounds like what Mike has done.
> >
> > If you 'replace' (<right click>/Replace Symbol) all the original entries
then the original '<SYMBOLDEF id='??'>' entry will be removed leaving only the
new one.
> >
> > v2.70.00 seems to be the same.
> >
> > Hope that helps
> >
> > Phil
> >
> >
> > --- In tinycad@..., "Don Lucas" <Don.Lucas@> wrote:
> > >
> > > What version of TinyCAD are you using?
> > >
> > > The .dsn file is an ascii file containing XML statements. If there are
actually multiple definitions of a symbol in the design, then you should be able
to find it in the .dsn file by editing with text editor such as notepad. If you
locate such a problem, please send me a copy of the design file and any
information that you might have that would allow me to reproduce the problem.
> > >
> > > Thanks,
> > >
> > > Don Lucas
> > >
> > >
> > > --- In tinycad@..., "mkishinevsky" <mkishinevsky@> wrote:
> > > >
> > > > I am struggling with a problem that schematic accumulates multiple
SYMBOLDEFs for the same symbol. It is especially dangerous because I changed pin
length of a symbol at some point, but both versions are still in the .dsn file.
As a result, sometimes pins get disconnected from wires, especially when I
copy/paste schematic to a different file.
> > > >
> > > > Is there a way to clean up?
> > > > The menu item "cleanup" does not exists in newer versions.
> > > >
> > > > Thanks.
> > > >
> > > > mike
> > > >
> > >
> >
>