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-transfer-encoding;
        bh=jD7vsVnN9Yvs33YgUGUKCct0vcWmhMJgZ3j/NjKW124=;
        b=f9OdTAWXm/aC9WUIAVhKtYWNSnosb/+8RHY4RKGTrs8Ep0iJgiiInnyCtGsbPVqHSt
         Brj3MPAlPCsaYQZtzIBse0sU1ENFD/NJ4dmbx9yFoHBVehvj2//h79pFwCtnXByxZP0u
         TRNH7UY3zoDh3QDJ1AMjem0AnzYJ04ahva+QsRI5QwIWIl7lwKeK+FC+JXHfA5BbsfP4
         tsUW0KEM1V7e63bJn7doeanl0s+CMgLFpFfO5An0iTh5O2UNz2r+OlVRLwvFTogmIB5R
         TJDyE/QnygPmgcRQHhK+XzhNv+GtdbUDfEh3dRMikR1YJ6Y4B3UVVrxYeCqoBwkEJGN/
         YcuA==
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-transfer-encoding;
        bh=jD7vsVnN9Yvs33YgUGUKCct0vcWmhMJgZ3j/NjKW124=;
        b=AmFI0xsOGsXIUasv+mR0eNqZv4QRxwyPELDHbvU5RTgAGxC6T99i7uFKJ1+xiCj+A4
         Dq+XkF3bXDXVw6rUPvvX7mukpVTpkwbKbO9wWK4yzJ7gxdWCZvowksa1k8cmjrN0dilR
         pcmicLa3e09TvPHe58lBIFJ2cMNVH6Y8Z4OSZu70+NnYzntWpYVQjlKUB/9W77JzSPWK
         t5Ngxsgfg5v29dlDxroE+MCQUSwy/+rPiv8e64/kFamAmJ2DqLHww5XMrk3iyDg1n7qw
         yWEDDfCjhhrp8V2+ANSTQzM+ZgHmIiwz/NBkDxQg7Paq3aG1QE//bZMt0mVdZD0QkqEt
         In6g==
X-Gm-Message-State: AEkoousNxNke1mzVpXsLaCy0eatUJkECK7ZskEyLojqdo4Atyhv63DUXcA4g3bAtSbZEOw==
X-Received: by 10.28.185.202 with SMTP id j193mr15378998wmf.78.1470073555180;
        Mon, 01 Aug 2016 10:45:55 -0700 (PDT)
Date: Mon, 1 Aug 2016 19:45:50 +0200
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] Wilkinson splitter - how to implement and use?
Message-Id: <20160801194550.9fdd9547edb6572db6e70771@gmail.com>
In-Reply-To: <a7acaf21-df0d-d209-d053-fcc470762ea3@ecosensory.com>
References: <23abdc31 DOT 72365e7a DOT 572529a9 DOT 212e2 AT o2 DOT pl>
	<a5562efe70ac4b83b066facd19a46167 AT gwp>
	<20160801162742 DOT GA27552 AT recycle DOT lbl DOT gov>
	<20160801184707 DOT 7b3dda2d3c0d13e103a5ec59 AT gmail DOT com>
	<a7acaf21-df0d-d209-d053-fcc470762ea3 AT ecosensory DOT com>
X-Mailer: Sylpheed 3.5.0beta1 (GTK+ 2.24.25; x86_64-pc-linux-gnu)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
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
Precedence: bulk

On Mon, 1 Aug 2016 12:21:48 -0500
"John Griessen (john AT ecosensory DOT com) [via geda-user AT delorie DOT com]" <geda-user AT delorie DOT com> wrote:

> On 08/01/2016 11:47 AM, Nicklas Karlsson (nicklas DOT karlsson17 AT gmail DOT com) [via geda-user AT delorie DOT com] wrote:
> > I am pretty sure a flag exclude from connectivity test on the drawing primitives connecting pins would do the trick.
> >
> >
> >> > that would allow solving both Michael's problem, and the star-ground problem
> >> > that has been discussed sporadically over the years.
> 
> When we get to using the tools for printable electronics this comes up again, and that's soonish.
> 
> There will be a need for resistive layers that can connect, yet not trigger a short because of their
> attributes.  Such resistive layers would need to be inside a footprint boundary always to avoid big trouble.
> 
> To debug shorts when they are on board it might be good to temporarily make them invisible and nonconductive, yet still located
> at coordinates.  Or make a temporary save function that will draw them all back with all attribs after a set is deleted for 
> debugging purposes.
> 
> Then layout vs. netlist DRC checks could be a 2 step dance, where pin to pin connectivity is gotten with one, and
> all connectivity including "printed electronics" is checked only after the first is free of shorts.
> -- 

nonetlist should be needed very seldom and it would probably make sense to with a warning it have been used within the layout.