X-Authentication-Warning:	delorie.com: mail set sender to geda-user-bounces using -f
X-Recipient:	geda-user AT delorie DOT com
Mime-Version:	1.0 (Apple Message framework v1085)
Subject:	Re: [geda-user] Trace width - best practices?
From:	John Doty <jpd AT noqsi DOT com>
In-Reply-To:	<20121026001145.29502e3d@akka>
Date:	Thu, 25 Oct 2012 20:43:31 -0600
Message-Id:	<0BE3EC45-C7EB-45A6-86EB-373D130A7DCE@noqsi.com>
References:	<20121023192443 DOT GK524 AT fi DOT muni DOT cz> <CAKakQccEOLFD0bbe6ydry-6YN7xsvjJAcbrTSt6DAYHJN-ohrA AT mail DOT gmail DOT com> <20121024024222 DOT 5584aab6 AT akka> <20121024095322 DOT 6bf3d4af AT svelte> <20121026001145 DOT 29502e3d AT akka>
To:	geda-user AT delorie DOT com
X-Mailer:	Apple Mail (2.1085)
X-MIME-Autoconverted:	from quoted-printable to 8bit by delorie.com id q9Q2haNR000617
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 Oct 25, 2012, at 4:11 PM, Kai-Martin Knaak wrote:
>> 
>> Actually, being able to break a net down into some more structure
>> would be helpful for a lot of other things as well.
> 
> Sure. But the price to be paid in terms of data structure modification
> and changes to the file format seems pretty high.

I don't see why it would require file format modification. We can attach arbitrary attributes to net segments already. The problem is that the netlist back end can only access a certain processed subset of the data in the schematics.

John Doty              Noqsi Aerospace, Ltd.
http://www.noqsi.com/
jpd AT noqsi DOT com

- Raw text -