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=20161025;
	h=date:from:to:subject:message-id:in-reply-to:references:mime-version
	:content-transfer-encoding;
	bh=0FwpI79BghuqniDvDFrw3D5476BoQna9O8uo9vw7+fA=;
	b=kj03dZeuEcpd4ooX9z8JqAEButBh9u1j/zHgbx/EN/c9jj8PubMhkPiMenqVmghDt7
	EX+8eIhI5/lzXCzsr9OST7o0pH/bjpNLliLXAsPaJ+aiBpmukZ5K7JrexkkKswS8zTXe
	QYH5JNR52Jcp+J0WiQ+7vag812d2ihH53oEK/Y1krcsZ0DZYgZbar7rzexrdgHLpA1Rm
	qlFgO2z/B1cz6juR0z+ISD1E7wQayW3X3HVYpQ7/kc5S+DUWjrv+2jw+AVVCyncWedkS
	bEGXmj4N5Sz35CvS8rlFgg3Gcqd4MyLLTj7CziHwaFOnhgC+yIM0jtdMT0OeuK4vLtGo
	8Irg==
X-Google-DKIM-Signature:	v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=1e100.net; s=20161025;
	h=x-gm-message-state:date:from:to:subject:message-id:in-reply-to
	:references:mime-version:content-transfer-encoding;
	bh=0FwpI79BghuqniDvDFrw3D5476BoQna9O8uo9vw7+fA=;
	b=eUQGTTgZtPWZ/dngaLdTGbBG+K5T6prMgafrpW/fyC5hK1xbwz2gauQ6hKXzJEGcVt
	O57VL7q1IV6ojimFZ0vU4djWhNll+5fpIezBpxHFhWiBjKA3IOKuLbghJ7og+ZOEKSlj
	yD8q2SmGz3mOwBYCuvQvccknBKwV92ERi2PeGYwhGq8jySsY/saPMphvq+YvYNWq0sDq
	MBNTyvphAlszEDJWmNzFu74Cjpa7cpJJH+mgqMmQXIUTmpNvHBJiFrE1stntMtqxbA8v
	lnYMthKbckNbibYAFWg9LBRYYHGLASCOFRIxrkQiWtxfngp6WbyRqfHkBAg6vdLigX9c
	9DEw==
X-Gm-Message-State:	AKS2vOypxfWtp/DByoKBXI9sSiVYW9XrgpKWNFG6kkhG7jiz/rXVoSmu
	IhKdWZDfNu1YoWzI
X-Received:	by 10.46.5.130 with SMTP id 124mr5661990ljf.95.1497815449327;
	Sun, 18 Jun 2017 12:50:49 -0700 (PDT)
Date:	Sun, 18 Jun 2017 21:50:45 +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] Parameter substitution --> hierachy
Message-Id:	<20170618215045.7be1624f69a66f49ec1d27bb@gmail.com>
In-Reply-To:	<614f7601eb62dc51d8b416c313c939f8@tfsoft.org.ua>
References:	<98D1C4E4-581D-4A03-94E4-E0330960EADF AT wellesley DOT edu>
	<s6na8h89ydi DOT fsf AT blaulicht DOT dmz DOT brux>
	<alpine DOT DEB DOT 2 DOT 11 DOT 1607231941050 DOT 16188 AT nimbus>
	<s6n8tws1428 DOT fsf AT blaulicht DOT dmz DOT brux>
	<alpine DOT DEB DOT 2 DOT 11 DOT 1607232257250 DOT 1800 AT nimbus>
	<s6npoq4x9bx DOT fsf AT blaulicht DOT dmz DOT brux>
	<EA4BA0F4-6B70-4C17-B801-2BE99AB48AE8 AT noqsi DOT com>
	<s6nmvl7x6h6 DOT fsf AT blaulicht DOT dmz DOT brux>
	<20160724090420 DOT fc7353ebc390b8f46bb5ebfc AT gmail DOT com>
	<614f7601eb62dc51d8b416c313c939f8 AT tfsoft DOT org DOT ua>
X-Mailer:	Sylpheed 3.5.1 (GTK+ 2.24.31; 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

> Nicklas Karlsson (nicklas DOT karlsson17 AT gmail DOT com) [via 
> geda-user AT delorie DOT com] wrote 2016-07-24 10:04:
> >> >>> - Pins for subschematic symbols don't require a pinnumber= attribute,
> >> >>> and non-slotted pins don't require a pinseq= attribute.
> >> >>
> >> >> Have they ever required those?
> >> >
> >> > If you turn off hierarchy expansion gnetlist needs pin numbers, since
> >> > connectivity is identified by (refdes pinnumber).
> >> 
> >> Ok, sure, in that case they have netlist semantics attached.
> >> 
> >> And now I remember your problem with the substitution patch.  When
> >> hierarchy is not expanded, there will be nowhere to apply the
> >> substitutions.  Your spice netlister would need to transform the
> >> substitutions into instance parameters.  Is that difficult?
> >> 
> >> --
> >> Stephan
> > 
> > To transform the substitutions into instance parameters sounds like a
> > good solution because otherwise user is required to number pins even
> > though they have no particular meaning in a hierarchical symbol.
> 
> What was the agreement reached (if any) on the problem of parametrical 
> subcircuits?
> 
> Any plans to implement this in mainline gEDA/gaf or Lepton EDA?
> 
> I will gratefully test the relevant code (like this patches 
> https://bugs.launchpad.net/geda/+bug/911440) in my projects if there 
> will be at least a hint about the direction towards which this feature 
> will be developed.

I did like this on one circuit today:
  1. I made layout for "sub circuit" on a free square so that it could be selected with ordinary select tool.
  2. I selected and saved buffer as elements, filename "*S1/S1.pcb".
  3. Opened file "*S1/S1.pcb"
  4. Used find "S1/S1" and replace with "S1/S2".
  5. Saved file to "*S1/S2.pcb".
  6. The same for the third "sub circuit" but with filename "S1/S3".
  7. Pasted all three circuit into layout.

What is needed in file structure and software is to find which object belong to a particular "sub circuit", for example structured data or an attribute, I think Igor said this is possible. Then object are possible to find and select ordinary move, copy and paste could be used and this is useful even if there is only one "sub circuit" so it could be selected and moved. For several copies a method to copy changes from one "sub circuit" to others will be very useful. There must be a method to select which "sub circuit an object belong to and a selector then drawing traces would probably be very useful. Then a "sub circuit" is copied there must be rename mechanism and I am pretty sure a structured naming scheme will make life simpler, most often I guess a hierchical schematic is very useful.


Nicklas Karlsson

- Raw text -