| delorie.com/archives/browse.cgi | search |
| X-Authentication-Warning: | delorie.com: mail set sender to geda-user-bounces using -f |
| X-Recipient: | geda-user AT delorie DOT com |
| Date: | Sat, 10 Oct 2020 13:08:19 +0200 (CEST) |
| From: | Roland Lutz <rlutz AT hedmen DOT org> |
| To: | geda-user AT delorie DOT com |
| Subject: | Re: [geda-user] how to pass extra attributes from gschem to pcb |
| In-Reply-To: | <xnv9fiob2r.fsf@envy.delorie.com> |
| Message-ID: | <alpine.DEB.2.21.2010101304390.1226@nimbus> |
| References: | <xnv9fiob2r DOT fsf AT envy DOT delorie DOT com> |
| User-Agent: | Alpine 2.21 (DEB 202 2017-01-01) |
| 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 |
On Fri, 9 Oct 2020, DJ Delorie wrote: > Perhaps a way to put a list of attributes-to-be-copied into the .pcb > itself, which are somehow passed to pcbfwd? Or put such a list in the > .sch files? On Sat, 10 Oct 2020, DJ Delorie wrote: > So just naming an attribute "pcb:something=foo" causes "something=foo" > to be migrated into the element. I like both approaches. Unless there's some further argument in favor of (1), I'll implement (2). Roland
| webmaster | delorie software privacy |
| Copyright © 2019 by DJ Delorie | Updated Jul 2019 |