X-Authentication-Warning:	delorie.com: mail set sender to geda-help-bounces using -f
X-Recipient:	geda-help AT delorie DOT com
X-Original-DKIM-Signature:	v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=gmail.com; s=20161025;
	h=mime-version:in-reply-to:references:from:date:message-id:subject:to;
	bh=BHfzJGjCCbTFzcmSZxesMyR/HnTAPqV/vrUTfpzbo4s=;
	b=U0UeYqgV4iVeZJQnM3bfJRpKGunJ8pT+usSysKjD+TpmyBkPwU/LUzWgC2Cj95wjN7
	fOmReoikh0YD89MxzVgMjTMjdPeP6TiqigLWv0Mo0/h5I7/rioB1kBEuCAXaNv1Q5V59
	vWQDxJ9jvSpIbjEspVPBuHfmGEVFofwqB05+k4hyjC9pm0p1DHbTKKxJJJWUZNCTxdnD
	26L9xmmvfc3i4F219qapMjirjSSY6tFNfVgnBvih8fpO+jLLkInsmVAojXEBXDaH62Lc
	o2o6A/xC2u6NOyk0t4VXkaoltBgmGmv5rS4Jn7xBvfHKfAPxN/a6DrraerSMLnuuTgVp
	8A+w==
X-Google-DKIM-Signature:	v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=1e100.net; s=20161025;
	h=x-gm-message-state:mime-version:in-reply-to:references:from:date
	:message-id:subject:to;
	bh=BHfzJGjCCbTFzcmSZxesMyR/HnTAPqV/vrUTfpzbo4s=;
	b=MFUz/cvYwT2emgBxwSq1/4Pv+LL/2fzgo+2wUMIyxY0C1PhZcvrioDQB0USpAojss/
	BlusFFMxkEKQNuD77HGW4H+dQeabvDPfWXb9Tn81OdgoDyKbhnLH0Cqeia+s3eXCjsej
	r55+7ZoplUypZQLEyBGMrbZgtIBcd97hxvUUt+v4unCYZ8Q/nvkrKRyZGvU3iJkHD3it
	7IZuKq7qpTIzv69qKZkclMad9SIqpESAuJJLEKNQMFp4X5sT/u2W9yjhOskInfy0+OKU
	O7dd+VNvhXO77kRLCCzPFoi/vKFdDnb2FU+fqrbaj/UoYGK3ZSSUl4YIu9i+mHlRgLq6
	IyKA==
X-Gm-Message-State:	AMke39nHsC/cLYhL6lrb+4Ip189IkORpYujjL9rWwrRt8UoPKkqo5ObfLixbgvb21vvJAbWLfUBb9vM9tQjKRg==
X-Received:	by 10.223.141.229 with SMTP id o92mr12250527wrb.22.1487479580419;
	Sat, 18 Feb 2017 20:46:20 -0800 (PST)
MIME-Version:	1.0
In-Reply-To:	<4E40A607-349A-440A-8EB2-8DD478E510B5@noqsi.com>
References:	<CAEoZ9Hi01S7_QOETXLyBF1fOPeFUT_34YRiooJbbFSrDV956NQ AT mail DOT gmail DOT com>
	<FE10A69B-DB86-4182-A223-25AEE5FF697E AT noqsi DOT com> <CAEoZ9HgxR8qm9vfr6TUHgxPTeOGZ=a7Mc8NrwmPvJOLyXHa5fg AT mail DOT gmail DOT com>
	<CAJXU7q8-XPJ+9k3C4bVWvYe5ci1eFGrnNfeCBQoykhdWAM9s0g AT mail DOT gmail DOT com>
	<11BDEC14-5D1D-4157-B552-582C1E75D00E AT noqsi DOT com> <20170218180232 DOT GB23464 AT localhost DOT localdomain>
	<4FA4C5C8-4B56-493A-94AC-1D4920C201F3 AT noqsi DOT com> <20170218185614 DOT GA25608 AT localhost DOT localdomain>
	<FAF62B87-D375-416A-A008-77E9E33294C4 AT noqsi DOT com> <20170218202533 DOT GA6290 AT localhost DOT localdomain>
	<4E40A607-349A-440A-8EB2-8DD478E510B5 AT noqsi DOT com>
From:	"Vasily Olekhov (olekhov AT gmail DOT com) [via geda-help AT delorie DOT com]" <geda-help AT delorie DOT com>
Date:	Sun, 19 Feb 2017 07:46:19 +0300
Message-ID:	<CAEoZ9HgsPP_jw0Cq7=F3zazX+0UmjwX8WEKJkMAWq8Xmpb4_mQ@mail.gmail.com>
Subject:	Re: [geda-help] Please help with multiple-pages schematics
To:	geda-help AT delorie DOT com
Reply-To:	geda-help AT delorie DOT com
Errors-To:	nobody AT delorie DOT com
X-Mailing-List:	geda-help AT delorie DOT com
X-Unsubscribes-To:	listserv AT delorie DOT com

--f403045f530a006c920548dad40b
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Thank you everyone.
Yes, naming nets that span across the pages helps.

Yet, naming by hand most of QFP144 pins is quite labour-intensive.

On Sun, Feb 19, 2017 at 5:33 AM, John Doty <jpd AT noqsi DOT com> wrote:

>
> On Feb 18, 2017, at 1:25 PM, Vladimir Zhbanov (vzhbanov AT gmail DOT com) [via
> geda-help AT delorie DOT com] <geda-help AT delorie DOT com> wrote:
>
> > I don't know if I've understood you correctly, though IMO the same
> > pin must never appear in multiple places. Never!
>
> Then what=E2=80=99s the best way to specify the power rail for an opamp t=
hat may
> be slotted? Consider that we might want, in the future, to support more
> abstraction: you draw the circuit with an opamp, but you don't commit to =
a
> single or a slot in a dual or quad in the source schematic. You do that
> downstream, as separate netlister input. That=E2=80=99ll work if you draw=
 power to
> each opamp, and have the netlister check for consistency.
>
> John Doty              Noqsi Aerospace, Ltd.
> http://www.noqsi.com/
> jpd AT noqsi DOT com
>
>
>

--f403045f530a006c920548dad40b
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Thank you everyone.<div>Yes, naming nets that span across =
the pages helps.</div><div><br></div><div>Yet, naming by hand most of QFP14=
4 pins is quite labour-intensive.</div></div><div class=3D"gmail_extra"><br=
><div class=3D"gmail_quote">On Sun, Feb 19, 2017 at 5:33 AM, John Doty <spa=
n dir=3D"ltr">&lt;<a href=3D"mailto:jpd AT noqsi DOT com" target=3D"_blank">jpd AT no=
qsi.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D=
"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class=
=3D""><br>
On Feb 18, 2017, at 1:25 PM, Vladimir Zhbanov (<a href=3D"mailto:vzhbanov AT g=
mail.com">vzhbanov AT gmail DOT com</a>) [via <a href=3D"mailto:geda-help AT delorie.=
com">geda-help AT delorie DOT com</a>] &lt;<a href=3D"mailto:geda-help AT delorie DOT com=
">geda-help AT delorie DOT com</a>&gt; wrote:<br>
<br>
&gt; I don&#39;t know if I&#39;ve understood you correctly, though IMO the =
same<br>
&gt; pin must never appear in multiple places. Never!<br>
<br>
</span>Then what=E2=80=99s the best way to specify the power rail for an op=
amp that may be slotted? Consider that we might want, in the future, to sup=
port more abstraction: you draw the circuit with an opamp, but you don&#39;=
t commit to a single or a slot in a dual or quad in the source schematic. Y=
ou do that downstream, as separate netlister input. That=E2=80=99ll work if=
 you draw power to each opamp, and have the netlister check for consistency=
.<br>
<div class=3D"HOEnZb"><div class=3D"h5"><br>
John Doty=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 Noqsi Aerospace, =
Ltd.<br>
<a href=3D"http://www.noqsi.com/" rel=3D"noreferrer" target=3D"_blank">http=
://www.noqsi.com/</a><br>
<a href=3D"mailto:jpd AT noqsi DOT com">jpd AT noqsi DOT com</a><br>
<br>
<br>
</div></div></blockquote></div><br></div>

--f403045f530a006c920548dad40b--

- Raw text -