| delorie.com/archives/browse.cgi | search |
> And you need a way to distinguish them. I think we're underestimating the importance (and complexity) of that. > although slotting is arguably a messy feature rather than a clean > fundamental capability. So... what if we dumped slotting? What would schematics look like then? Do we assume/require that the user will create a schematic with a separate refdes for each gate in a package? That, of course means we need to set some expectation of what <downstream>'s package refdes would look like, but it would mean that refdes is unique enough... ... except for cases where the user splits one package up into multiple symbols because of complexity, like breaking up an MCU or splitting out power pins. Are there cases where a package contains two identical copies of something complex enough to each be broken into separate symbols? And the user still needs some mechanism to connect up power/ground pins on multi-gate packages. > I do believe we need a way to override pin attributes in instances. +1 > Embed the symbol and edit? Perhaps this is the right solution for an as-built anyway, as it locks in the symbols it was built with.
| webmaster | delorie software privacy |
| Copyright © 2019 by DJ Delorie | Updated Jul 2019 |