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] how to pass extra attributes from gschem to pcb |
In-Reply-To: | <CAC4O8c-w=TaSQPbedr8nnoNBoOed6zywhfNv9-TD+_wy0w5r1g@mail.gmail.com> (geda-user@delorie.com) |
Date: | Fri, 09 Oct 2020 22:06:34 -0400 |
Message-ID: | <xnzh4uomvp.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 |
> How would people feeling about adding something like misc or > user_attribute_string (or something) to the list? 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? I'm just thinking, if we're bumping into this now, it would be a shame to not make it flexible enough to support *any* attribute, and not just a continuously growing but fixed list. If there's a simple way to make it flexible, that would be better.
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |