delorie.com/archives/browse.cgi | search |
X-Authentication-Warning: | delorie.com: mail set sender to geda-user-bounces using -f |
X-Authentication-Warning: | envy.delorie.com: dj set sender to dj AT delorie DOT com using -f |
From: | DJ Delorie <dj AT delorie DOT com> |
To: | geda-user AT delorie DOT com |
Subject: | Re: [geda-user] why pinnumber in sym pins? |
In-Reply-To: | <22B45B52-6B12-4985-A8AF-3010B6F709A4@noqsi.com> (message from John Doty on Tue, 26 Dec 2017 12:42:46 -0500) |
Date: | Tue, 26 Dec 2017 12:47:06 -0500 |
Message-ID: | <xninctpejp.fsf@envy.delorie.com> |
MIME-Version: | 1.0 |
Reply-To: | geda-user AT delorie DOT com |
Errors-To: | nobody AT delorie DOT com |
X-Mailing-List: | geda-user AT delorie DOT com |
X-Unsubscribes-To: | listserv AT delorie DOT com |
John Doty <jpd AT noqsi DOT com> writes: > For big designs, what I really want is the ability to draw generic, > abstract schematics and then forward annotate them into concrete, > as-built schematics. My script almost does that. It maps refdes/pinlabel to pinnumber, and adds all the package-specific attributes. It doesn't annotate schematics, but that shouldn't be hard to add. http://www.gedasymbols.org/user/dj_delorie/tools/pinmapper.html
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |