On Dec 15, 2006, at 11:16 AM, Peter Clifton wrote:
On Thu, 2006-12-14 at 21:08 -0500, Stuart Brorson wrote: [snip]This would overwrite the attribs of the pin located at 3300 1600 3600 1600. In particular, it would overwrite pin 13, making it pin 15 in the schematic. To effect this, gnetlist would just need to recognize that the pin at location 3300 1600 3600 1600 is being overridden by the attribs between the {}, and then build the correct netlist accordingly. Gschem would need to display the correct pinnumber also, meaning that the internal datastructure must support this overwriting. Or do we need to do something more involved?At first glance, it seems that this does uniquely solve which pin is being over-ridden, however you do have difficulties when a symbol is updated externally. (.sym file changed) When you re-load in gschem, there is no way to tell (other than guess) where the pin you're over-riding is in the new symbol.
But that problem is already present. If you move the tip of a pin when you revise a symbol, the new symbol won't connect to existing schematic nets. So, the coordinates of the tip of a pin really are a unique, invariant identifier of the pin for all practical purposes.
So I think pins really want to be over-ridden by a name, or number. Something which won't change when editing the underlying symbol unless the user wants to alter which pins are over-ridden. Peter C. _______________________________________________ geda-dev mailing list [email protected] http://www.seul.org/cgi-bin/mailman/listinfo/geda-dev
John Doty Noqsi Aerospace, Ltd. [EMAIL PROTECTED] _______________________________________________ geda-dev mailing list [email protected] http://www.seul.org/cgi-bin/mailman/listinfo/geda-dev
