X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f
X-Recipient: geda-user AT delorie DOT com
Date: Fri, 16 Nov 2012 03:39:46 +0100
From: Kai-Martin Knaak <kmk AT familieknaak DOT de>
To: geda-user AT delorie DOT com
Subject: Re: [geda-user] slotting
Message-ID: <20121116033946.1b7bc23c@akka>
In-Reply-To: <Prayer.1.3.5.1211141555060.15335@hermes-1.csi.cam.ac.uk>
References: <CACPio-7O1OS0Z-NkOJmzTvxSFf+v9j6yFM8F6xRXeZvTjDUK8A AT mail DOT gmail DOT com>
	<50A2B84F DOT 4080204 AT laserlinc DOT com>
	<CACPio-4+wJj6WY-GsJhskmZicM1mn6YKoRc4kVVP9ABXLpZYYg AT mail DOT gmail DOT com>
	<50A3AAA6 DOT 1080704 AT laserlinc DOT com>
	<CACPio-4cDVS+vmowijmZ6Y9E0+rXoEimc9ugZqTPGvOKQvoqow AT mail DOT gmail DOT com>
	<Prayer DOT 1 DOT 3 DOT 5 DOT 1211141555060 DOT 15335 AT hermes-1 DOT csi DOT cam DOT ac DOT uk>
X-Mailer: Claws Mail 3.8.1 (GTK+ 2.24.10; x86_64-pc-linux-gnu)
Mime-Version: 1.0
Content-Type: multipart/signed; micalg=PGP-SHA1;
 boundary="Sig_/+te4IIMm7gb1ocC87uUJv7v"; protocol="application/pgp-signature"
X-Provags-ID: V02:K0:H3AqcCeriFrMqLjPGa3FkMlT4pdvoe6nC8dEsI6l25g
 S8ss4BSwYJ+Q05f8/p1oGRLoW0QnuRmKWOqpdfShIo6vTxDTWA
 Z/waA2lKIazmUxCAPr0i4te8ukdu+YHkousH3O1BRjxDfJPO5N
 wvgrcbgXII7a8O9q1WfUBk9wehKrqqipgiTl3fUr7nF9lT7r7l
 9lugS2ZPUIYNovEnU3tVxOzi2twG3BpjKLG9FJ0S7F/o39wssL
 S53CJgL4b4IQ7cZ5yk1KFxRZ0hZlmuOzf/yBZoIMMaDm8KFsmp
 Xa2PDy4q51DeDZQEZXIM+yjzGuONU3ubsXY5oC7+pMZgI/1TQ=
 =
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

--Sig_/+te4IIMm7gb1ocC87uUJv7v
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: quoted-printable

"Peter C.J. Clifton" <pcjc2 AT cam DOT ac DOT uk> schrieb am 14. November 2012:

> This probably won't play well with the renumber tools out there,

Specifically, it does not play well with the built-in renumber tool of
gschem. Attributes -> autonumber-text will always make all refdeses
different even if they were deliberately set to the same value. This is
one of my "favourite" gschem warts.=20


> Finally.. if you do use multiple symbols anywher, there is (or was?) a=20
> problem you have to work around, in that when picking up the symbols
> to retrieve attributes from (e.g. for forwarding to PCB layout), it
> was not clear which of the two symbols would be scanned for attributes.
>=20
> To get around this, add the "footprint=3D..." and any other attributes
> you need to be "machine" readable to both halves of the symbol.

This kind of redundancy creates maintenance issues. E.g. consider a
7414, which is a package with six inverters. In the schematic these
would be six times a NOT symbol plus a symbol for the power pins. All of
them have to be edited if the footprint is to be changed from DIP14 to
SO14.=20
I like to make the footprint value visible in the schematics.
The requirement for footprint attributes on each and every symbol adds
to the clutter in the schematic.

=20
> (If this issue hase has been resolved already, someone please let me
> know).

It has been alleviated, but not quite resolved. Current gnetlist warns
if it finds different footprints to an attribute. However:

* which value gnetlist picks, depends on the order the symbols were
  entered in the schematic. I wrote a patch that makes sure, gnetlist
  output never ever depends on the order of symbols. This patch was not
  accepted by the devs. I still think, this dependence on order is a bug.

* import-schematics in pcb does not show the warnings

* a missing footprint attribute is treated like a footprint with value
  "#f". This effectively enforces to set the footprint attribute on
  every symbol. Else, gnetlist output will be swamped with warnings.=20

---<)kaimartin(>---

--=20
Kai-Martin Knaak

--Sig_/+te4IIMm7gb1ocC87uUJv7v
Content-Type: application/pgp-signature; name=signature.asc
Content-Disposition: attachment; filename=signature.asc

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iEYEARECAAYFAlClp3IACgkQt9RkiGwLn1MbGACeP/Qh/zC62hmgNgSOl/BiN7EK
JYQAn2Yt/nWPY9RdbPIu3LpI2kYA5tTX
=E3x1
-----END PGP SIGNATURE-----

--Sig_/+te4IIMm7gb1ocC87uUJv7v--