X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f
X-Recipient: geda-user AT delorie DOT com
X-Virus-Status: Clean
X-Virus-Scanned: clamav-milter 0.98.4 at av01.lsn.net
Message-ID: <54E354D4.3040509@ecosensory.com>
Date: Tue, 17 Feb 2015 08:48:52 -0600
From: John Griessen <john AT ecosensory DOT com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Icedove/31.4.0
MIME-Version: 1.0
To: geda-user AT delorie DOT com
Subject: Re: [geda-user] Star connection points in PCB?
References: <1502170242 DOT AA18887 AT ivan DOT Harhan DOT ORG> <alpine DOT DEB DOT 2 DOT 00 DOT 1502170501000 DOT 7324 AT igor2priv>
In-Reply-To: <alpine.DEB.2.00.1502170501000.7324@igor2priv>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Reply-To: geda-user AT delorie DOT com

On 02/16/2015 10:33 PM, gedau AT igor2 DOT repo DOT hu wrote:
> Proposal 3
>
> Add a component flag in pcb that tells "there is no short between the pads of this component, even if they overlap!", then draw
> the actual star out of pads. The starpoint is an explicit component in pcb and an explicit symbol on the schematics. Each net has
> its own dedicated pin, No short anywhere, so won't interfere much with find.c, except that flag, which should be relatvely easy to
> implement (saying that after intconn, a patch f mine doing the opposite). Drawbacks:
>
>   - the same pin numbering and back-annotation problem that you have with connectors
>
>   - the star symbol/footprint will have explicit number of pins, you may end up unused pins or will have to replace with the next
> bigger if more nets are to be connected


I like this because the netlist generated is sane.  One sees the converging of power nets at a symbol, and that
symbol can relate to a physical location.  The "auto" feature of 2. could cause accidental mystery to debug...