delorie.com/archives/browse.cgi | search |
> > You also wrote: > > > > > What I want is a way to reliably map an instance of a device with its > > > schematic symbol, without the user having to jump through hoops to > > > satisfy some hidden "rule" about how to create schematics. > > > > How is it hard for a user to understand that symbols need to be > > distinguishable at the schematic level? > > From the user's point of view, they're distinguishable. There's this > one, and that one :-) Why should we force the user to decide > packaging, slotting, and unique numbering, right at the beginning, > when they're just tossing a design together? Even as late as layout, > they could change the packaging and thus change the slotting (for > example, switching from a quad-nand to two dual-nand packages). You are absolutely right packaging, value and slotting is usually not the first step. Nicklas Karlsson
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |