The do not break current designs can be taken care of by a convert current library to new, and a script that converts schematic from old symbols to new. Symbols converted would need an attribute old position to new position x-y diff for the schematic conversion script, or something, to work. We just need to get moved over to the new style origin, and then stay there. The origin would not always have to be on pin 1, it could be on the first pin defined, or something. We are just talking a convention here not a law. There will always be exceptions.
Ross Amans Hardware Design Engineer Biometric Access Co 512-426-9252 (cell) -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Kai-Martin Knaak Sent: Thursday, May 29, 2008 4:52 PM To: [EMAIL PROTECTED] Subject: Re: gEDA-dev: origin in gschem On Thu, 29 May 2008 14:22:21 -0500, Amans,Ross wrote: > I think the pin 1 end of the wire used as origin would give a reliable > point for schematic drawing placement use, as then adding pins, etc in > the symbol would not move the part or disconnect the part Nor would > adding properties / text, etc in the symbol. Ok, origin at the active end of pin 1 seems like a sensible selection for most symbols. But there are exceptions. Some symbols are purely graphical with no pin at all. However, these symbols obviously cannot break the nets of a schematic. Then there may be symbols with no pin 1 but other pin numbers. Some of my sub sheet symbols happen to have no number one pin. As my design evolves, I add and remove in- and out- pins as needed. A necessary constraint is, that the interpretation of symbols should not break with symbols currently in the library. One way to make sure they don't break, is to assume their origin is at 0/0. > Imagine placing a symbol, and then fixing a typo by adding a > small l in some small text at the symbol drawing bottom, causing the > whole symbol to shift in the schematic by a little bit. Not good. This is almost the situation we have now. Only difference is that the translation is done explicitly with the "translate component" command. ---<(kaimartin)>--- -- Kai-Martin Knaak http://lilalaser.de/blog _______________________________________________ geda-dev mailing list [email protected] http://www.seul.org/cgi-bin/mailman/listinfo/geda-dev _______________________________________________ geda-dev mailing list [email protected] http://www.seul.org/cgi-bin/mailman/listinfo/geda-dev
