X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f
X-Recipient: geda-user AT delorie DOT com
X-Injected-Via-Gmane: http://gmane.org/
To: geda-user AT delorie DOT com
From: Kai-Martin Knaak <kmk AT familieknaak DOT de>
Subject: Re: [geda-user] A lesson from gnet-makefile
Date: Thu, 22 Oct 2015 12:19:32 +0200
Lines: 24
Message-ID: <n0ad7l$79l$1@ger.gmane.org>
References: <DA7D969B-6516-4633-831C-FFADA38E1807 AT noqsi DOT com> <CAM2RGhRN5S1KZCNFQwoVTPg3=mC5xrK2z9XTOpWwPuF0iVS+Rg AT mail DOT gmail DOT com> <73ED29DA-968B-4675-9B00-125E03683C9B AT noqsi DOT com> <CAM2RGhSvpVvboJ-gdyrojAzggFEBnAr30CKNQBefjci-PA1n6g AT mail DOT gmail DOT com> <201510220112 DOT t9M1Ccfq013731 AT envy DOT delorie DOT com> <CAM2RGhQhNkShqtN8uyCSd7R+V4FgLXDZTvTC2RTdmKF7C_8ndA AT mail DOT gmail DOT com> <201510220136 DOT t9M1a5Uw015222 AT envy DOT delorie DOT com> <CAM2RGhQOpnBXbZXngNq=RcQTZN=UrU+PGzTZ9AC=xKNfu_zQkQ AT mail DOT gmail DOT com> <201510220149 DOT t9M1nrIe016145 AT envy DOT delorie DOT com> <CAM2RGhQ26+gpcAeTdgJpBEh0egOGLYcpizQ+B6kfTQLowEk5xQ AT mail DOT gmail DOT com> <20151022023002 DOT GA25952 AT recycle DOT lbl DOT gov> <20151022090751 DOT ecb5bc25c7d968646dea2e85 AT gmail DOT com>
Mime-Version: 1.0
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7Bit
X-Complaints-To: usenet AT ger DOT gmane DOT org
X-Gmane-NNTP-Posting-Host: a89-182-218-119.net-htp.de
User-Agent: KNode/4.14.1
Reply-To: geda-user AT delorie DOT com

Nicklas Karlsson  wrote:

> Yes, only problem with star ground symbol in gschem is how many pins
> it should have. In pcb for many cases it would make sense with one
> common connection point.
> 
Last time this topic surfaced on the mailing list the most practical 
suggestion was to exploit a pecularity of text in copper: 
The connection check of geda-pcb completely ignores letters. Insert a 
large "-" and make regular tracks overlap with the character but not 
connect to each other.

This is of course an abuse of a missing feature (connection check of 
strings in copper) which might break if/when somebody takes the time 
to fix it. But at least it works now. 

And it gives a hint for a second best solution: Add a tag "ignore-for-
connection-check" which can be attached to a track segment. This would 
of course also not check for unwanted connections to the tagged 
segment. But since it is an explicit localized exception, the risk is 
manageable. After all, we live with not connection checked text all 
the time...

---<)kaimartin(>---