Some thoughts on the underlying data model (symbols)

Everywhere I see a list of symbols - the symbol editor, add symbol dialog etc. - there are several pin number variants cluttering the list. I would rather have one generic symbol and choose the pin mapping separately, rather than having several “generic” symbols which actually aren’t generic because they leak implementation detail (symbol<->footprint pin mapping) into the user interface, and espcially into the symbol name itself.

I think it has been already said that those symbols which are meant to be generic actually aren’t generic because you’re required to know the footprint pin numbering when you select the symbol, or have a symbol name which conveys wrong information.

And some symbol groups don’t even have all possible pin order combinations.

1 Like