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=googlemail.com; s=20161025;
	h=mime-version:in-reply-to:references:from:date:message-id:subject:to;
	bh=CQrZeudgOulx4FkMikA4fOsjv7xsIQ859WQ1F2wRcFc=;
	b=cZyiM4u4Kqag7LBUZcI3RmuEMzUOXY5HsRGTMDpErFt4Pu0J6X6phei3OskwkRVx6R
	6aLx7gwFDS3Jugnlw1EXvxqOHXNi6re6lHtgD9gAVB2Kjkhf4Ai2lCz3eVC1dY05DXB0
	m9/RKHy+AwkMuC6Dg800/jXm6jmufm4Ffq8Mym2nlwdbV92mQPUMlkF3PdbguP5HhVD5
	aaE1g4P/HENOH+llGR7+Gee1ik2uWG9gOdbosWFUOHYoqImppXwYg00fJ+SDGi1fVAZC
	48gR4asnAaihZYGBDt3k0FqRexnF5riTa2tFXAepLhADC4A/cxAVKY53D46DfBaArs2T
	/Npg==
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=CQrZeudgOulx4FkMikA4fOsjv7xsIQ859WQ1F2wRcFc=;
	b=Xn0tUttzM3MCAr+u/UxpW/YTS+or8XiRlQUFXhbJsgfxLG3RwjFhjqH97a2lsHhfMr
	PFYkERemErCzgCxtoP6CSBxan8n2/cVPPS/gLwKqqWsLFfENK8SkZE+F15Ltagu9wSzw
	WNUwVQLq6U+dJY7IbOW0q2G0lCjMfjZx5FHkRhENRiAXB3P4BBr7SuW9EE1smKpLklh5
	/A3wZwwDaFWarHjxc3Mj5GGdQhkAft2F9PJ8G1e+mUZtV5KMRwm2zxlvhMktaUzZbqTU
	A8L50umiKdJesd6henB2+SvYPyyBqZIaiGlq/Rh/Xzzb3DobYC4E76i3MkV7EF+TxNGi
	xVWw==
X-Gm-Message-State:	AMke39nGEMHRklH/MpMqWd4kw5Wi7NPSaFpgUuD6aAUjy1xDM08m9TXUai+LFO+0xr7dQUAcX/qxoAGjjM5Efw==
X-Received:	by 10.200.41.198 with SMTP id 6mr14581242qtt.130.1487453921365;
	Sat, 18 Feb 2017 13:38:41 -0800 (PST)
MIME-Version:	1.0
In-Reply-To:	<20170218205206.5825C812BA6B@turkos.aspodata.se>
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>
	<20170218205206 DOT 5825C812BA6B AT turkos DOT aspodata DOT se>
From:	"Peter Clifton (petercjclifton AT googlemail DOT com) [via geda-help AT delorie DOT com]" <geda-help AT delorie DOT com>
Date:	Sat, 18 Feb 2017 21:38:40 +0000
Message-ID:	<CAJXU7q_T-Vw8bHy4_LFU-ehb3GcWHCahOqR_w4P1DOhaEjTcAg@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

--001a1141068c9a57970548d4da97
Content-Type: text/plain; charset=UTF-8

On 18 Feb 2017 20:53, <karl AT aspodata DOT se> wrote:

Vladimir:
...
> though IMO the same pin must never appear in multiple places. Never!
...

I don't see why not, as long as you don't connect the pin in more than
one of thoose places. If you have a ban on same pins in multiple places
you'll have more work generating symbols for devices with high pin
count.

Regards,
/Karl Hammar



Hi guys,

Not to single out any one email (had to pick one to reply to)... but I just
noticed this question was on geda-help, not geda-user.

Whilst the boundaries are blurred, we have probably strayed off topic for
this list. Let's focus on the "help" part, and save software design
discussions for a more appropriate forum.

Regards,

Peter Clifton

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

<div dir=3D"auto"><div><br><div class=3D"gmail_extra"><br><div class=3D"gma=
il_quote">On 18 Feb 2017 20:53,  &lt;<a href=3D"mailto:karl AT aspodata DOT se">ka=
rl AT aspodata DOT se</a>&gt; wrote:<br type=3D"attribution"><blockquote class=3D"=
quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1=
ex">Vladimir:<br>
...<br>
<div class=3D"quoted-text">&gt; though IMO the same pin must never appear i=
n multiple places. Never!<br>
</div>...<br>
<br>
I don&#39;t see why not, as long as you don&#39;t connect the pin in more t=
han<br>
one of thoose places. If you have a ban on same pins in multiple places<br>
you&#39;ll have more work generating symbols for devices with high pin<br>
count.<br>
<div class=3D"elided-text"><br>
Regards,<br>
/Karl Hammar<br></div></blockquote></div></div></div><div dir=3D"auto"><br>=
</div><div dir=3D"auto"><br></div><div dir=3D"auto">Hi guys,</div><div dir=
=3D"auto"><br></div><div dir=3D"auto">Not to single out any one email (had =
to pick one to reply to)... but I just noticed this question was on geda-he=
lp, not geda-user.</div><div dir=3D"auto"><br></div><div dir=3D"auto">Whils=
t the boundaries are blurred, we have probably strayed off topic for this l=
ist. Let&#39;s focus on the &quot;help&quot; part, and save software design=
 discussions for a more appropriate forum.</div><div dir=3D"auto"><br></div=
><div dir=3D"auto">Regards,</div><div dir=3D"auto"><br></div><div dir=3D"au=
to">Peter Clifton</div></div>

--001a1141068c9a57970548d4da97--

- Raw text -