On Mon, Sep 29, 2008 at 2:24 PM, Peter Clifton <[EMAIL PROTECTED]> wrote: > Ok, fair enough. Heavy symbols is another way to go about things. I was > talking about the possibility of using lighter symbols in the the > library, then associating more specifics in the schematic.
This is how i do in in my now-languishing abstract symbols branch. > You could > also attach the specifics in a "heavied up" symbol file if so desired. I don't maintain a symbol-specific "heavified" symbol though; only a *part*-specific heavified one. Best re-re-re-explained by example: the "light" symbol is a generic NAND gate with no specific pin numbering or other attributes, whilst the "heavy" symbol is a specific part, a 1983-issue 74H00, which specifies the mapping between each slot's pin functions and the part's pin numbers. This allows different kinds of devices to be represented as slots in the same part. > If the symbols start really light, don't you find you need to have > multiple resistor symbols, transistors, diodes etc.. once you've heavied > them up? Not necessary. Using the scheme-callback slot chooser trees (*), you can pick a particular *class* of resistor part and the leaf node that you pick out of the tree will instantiate a resistor of a particular value, tolerance, whatever. (*) To make this work the way I want add-component-at-xy needs to be able to query the user for an x,y pair somehow. Or just place them randomly. > I'm sure it would be fairly easy to have gschem make a copy when > selecting a symbol, but I wouldn't expect that the name ends up correct > without user input. Why would one want a *copy*??? _______________________________________________ geda-dev mailing list [email protected] http://www.seul.org/cgi-bin/mailman/listinfo/geda-dev
