X-Authentication-Warning:	delorie.com: mail set sender to geda-user-bounces using -f
X-Recipient:	geda-user AT delorie DOT com
X-Original-DKIM-Signature:	v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=gmail.com; s=20120113;
	h=date:from:to:subject:message-id:in-reply-to:references:mime-version
	:content-type:content-transfer-encoding;
	bh=dL545jWNFf4fgyPRK5WmA8ADB2kdC08xVwpoTomEy0A=;
	b=Vj0KF5ZaDQAYF5n86c4OqeAQcg6xLjKeWt5VtKN7OHNd8v9y2ad7+fVKU3ua4UNxJm
	tac4/3X+GUhAWp0aSSDkMNwPXHr4SDLMU6GfGJdaGmdJkEe0dNuOMRQgkvSLum9SWM7x
	nxTsxiS+z8VAh4EnCsV8vssi64rqY/P3mf/4tF0NoD+eTsp89GBzVIn2Q7rP1dVAXgUD
	goCKvELPJNVfYMfrOzeUewiZzUokgm659yAJkUISJi82KPqBTnPyeUw6koO1vl3F3mZi
	9V3VBlDxSrjjfD3anaWcQYHDHvjjin0cnH95/Fjmnm0f3nCoAu/Kl1igo7G6m8f9tsGQ
	dGlQ==
X-Google-DKIM-Signature:	v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=1e100.net; s=20130820;
	h=x-gm-message-state:date:from:to:subject:message-id:in-reply-to
	:references:mime-version:content-type:content-transfer-encoding;
	bh=dL545jWNFf4fgyPRK5WmA8ADB2kdC08xVwpoTomEy0A=;
	b=nEZeqFyZv+ekJxJCFdIH35pWPvLQvCdMmpt6HA/isz30jR1+trkeIx8zVwJhxzrmND
	vG7M0frWq0UXmoBd9z96iTYjAvuBwB+ZevoXQCHi/8Q2iQdRlP25/qhPG7ajx1QKrHNQ
	uCq6haJR/S/p4/zeOhMWkibGQjr181wWlsN+sCw52vZiPoUUzbT0nFXjKbF6wsst8770
	6/UpZ+anYDe5ZU+kdpSqSjWfTVgqUlNSrDEk9ZE/QYmLNAXJwqZ0w6iiAWSDRG4GujsL
	GCEUyNpHlZmcJLlL3eKfBCoHr4IMcFi9mB8DGBsBwvPI3uvkBPGrw+n9N62JXFrmOvO1
	IavQ==
X-Gm-Message-State:	AG10YOT1CqScN05pEel+ULBlbVS5Av/dY2qOnjdlmB2E39vxzv4muN88YPJbZB8Q8s3IHg==
X-Received:	by 10.28.48.137 with SMTP id w131mr6039872wmw.73.1454438120230;
	Tue, 02 Feb 2016 10:35:20 -0800 (PST)
Date:	Tue, 2 Feb 2016 19:35:14 +0100
From:	"Nicklas Karlsson (nicklas DOT karlsson17 AT gmail DOT com) [via geda-user AT delorie DOT com]" <geda-user AT delorie DOT com>
To:	geda-user AT delorie DOT com
Subject:	Re: [geda-user] The nature of gEDA layers
Message-Id:	<20160202193514.56b74a52d101cdbc3d1d1d5b@gmail.com>
In-Reply-To:	<s6nvb6758k7.fsf@falbala.ieap.uni-kiel.de>
References:	<alpine DOT DEB DOT 2 DOT 00 DOT 1601180756390 DOT 9035 AT igor2priv>
	<CAC4O8c9UKLsh5FAAwUMEtHThKH-w3gUmCU2i9dRW9igkyRt-TQ AT mail DOT gmail DOT com>
	<CAJZxidDmjMtd_fKvR5qZVRa+hwDUbvfaz79oZjkBgDuE1m8RBg AT mail DOT gmail DOT com>
	<56A961BC DOT 3040405 AT ecosensory DOT com>
	<CAJZxidC=nbxAinOtpfGHHqwPXbEMrhfat7jKgA9KBp3EVVg4_Q AT mail DOT gmail DOT com>
	<s6nbn863xlu DOT fsf AT blaulicht DOT dmz DOT brux>
	<56A9E416 DOT 8080500 AT ecosensory DOT com>
	<20160128124020 DOT 8f2f33210481f637a696f5d0 AT gmail DOT com>
	<CAJZxidD7=NE+Q3FGOU+ER3Xh7TRskEPRTKa=yrwUm51_VaYw0A AT mail DOT gmail DOT com>
	<20160128164922 DOT 7bd920859ab8462f8abb0f40 AT gmail DOT com>
	<s6ny4b9r3x7 DOT fsf AT falbala DOT ieap DOT uni-kiel DOT de>
	<20160128191943 DOT d3f06f258e112a8d7d532327 AT gmail DOT com>
	<s6nio2d2yr0 DOT fsf AT blaulicht DOT dmz DOT brux>
	<20160201113121 DOT 9e1229dc74b565f082c3bfba AT gmail DOT com>
	<n8pqa8$5fb$1 AT ger DOT gmane DOT org>
	<20160202102831 DOT 87be1281db69271eaf892fc9 AT gmail DOT com>
	<s6nh9hr9ssr DOT fsf AT falbala DOT ieap DOT uni-kiel DOT de>
	<20160202173714 DOT 071b35be76f3179b3e4f493c AT gmail DOT com>
	<s6nvb6758k7 DOT fsf AT falbala DOT ieap DOT uni-kiel DOT de>
X-Mailer:	Sylpheed 3.5.0beta1 (GTK+ 2.24.25; x86_64-pc-linux-gnu)
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

> > Now I got it, depth is useful to mix dark and clear. It is useful for
> > example to draw thermals but ror the most cases it should not be
> > needed.
> 
> Almost every copper trace will be have a polygon clearance attached.
> 
> Line {
>   Attribute{routingstyle="default"},
>   Path{(x1, y1), (y2,y2), ... },
>   Stroke{ layer="top", ends=round, depth=100, width=10mil },
>   Stroke{ layer="top", ends=round, depth=-500, width=30mil },
> }

It would make most sense to assign routing style per net although on a few occacions every now en then it useful per trace. One example is current shunt there signal traces are run separate with a lot thinner width.

Even tough it proceed slowly I have started to look at different clearance values for different nets. There will be a need for each net with a polygon clearance for each other net which may be optimized to each other net with polygon on current layer. I am planning routing style or at least clearance values per net. For an inverter logic is usually connected to the negative potential and for logic signal levels close to this voltage only a small clearance is needed. Between negative and positive rectified value their is need for larger clearance. Between any of the high voltage traces and protective earth there is legal requirements of minimum clearance.

> A polygon would be at depth=900.  The Line{} first clears a hole into
> the polygon and then draws a trace into the hole.  The hole would not
> cut through other lines or pads, only through the polygon below.

I think pcb/gpcb need to keep track of polygon depth automatically. Any copper object may make a cut out of clearance value larger then copper drawing primitive in a polygon but not in any other object. For drawing thermals or if needed other such more complicated objects I guess there is a need for local depth but can't, or is knowledge of polygon depth needed to get thermals correct for example then intersecting edge of polygon? Or for a close trace?

> Same for Vias stacks.  If you edit such an object, it would make a copy.
> But if you edit the routing style, all objects still referring to it
> would change.  The routing style tool would ask if you intend to change
> those 423 objects, or better bump the serial number of the style and
> keep those objects to refer to the old values.

Sound perfect although I do not understand why serial number need to be bumped to keep old values.


Nicklas Karlsson

- Raw text -