Mail Archives: geda-user/2015/10/19/15:30:53
--Apple-Mail=_FABC8C7D-1ACC-4D72-9CD5-873293ACC47D
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
charset=windows-1252
On Oct 19, 2015, at 12:58 PM, DJ Delorie <dj AT delorie DOT com> wrote:
>=20
>> Well, I think that's a logical requirement, not a mere desire.
>=20
> I'm glad you agree with yourself. We're back to my original
> supposition, that *if* it's required, *one* of the options is a UUID.
>=20
>>> No, (3) only requires a UUID be assigned to each symbol as it's =
instantiated.
>>=20
>> Until you realize that users make copies of things using multiple
>> methods, and the intent of the copy may be to move the circuitry or
>> to duplicate it. Then, it still requires clairvoyance.
>=20
> We've discussed this in the past, and generally agree that "path to
> object in design" needs to be part of the uniqueness, in order to
> differentiate between one symbol showing up in multiple places in a
> heirarchy. This plus "unique on page" (as long as the key to
> uniqueness doesn't change over time) is probably sufficient to
> uniquely correlate an instance in <downstream> to one symbol in the
> project.
You forget that one way to make a variant page is =93cp page1.sch =
page2.sch; gschem page2.sch=94. Gschem can=92t know that you=92ve done =
this, but it is a useful technique when you have repetition with =
variation. Another interesting case is where you copy/paste to a =
different page. These are only the cases I can think of right now.
Once you=92re enumerating use cases, trying to come up with a solution =
to each one, you=92re not thinking flexibility anymore.
> But we also generally agreed that a heirarchical schematic
> would need to be flattened to produce an as-built anyway, which limits
> that problem somewhat.
>=20
John Doty Noqsi Aerospace, Ltd.
http://www.noqsi.com/
jpd AT noqsi DOT com
--Apple-Mail=_FABC8C7D-1ACC-4D72-9CD5-873293ACC47D
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
filename=signature.asc
Content-Type: application/pgp-signature;
name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail
-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - https://gpgtools.org
iQIcBAEBCgAGBQJWJUTNAAoJEF1Aj/0UKykR7+UP/jq9CygfMJIFiFdyzoKAifsR
nwiT5Y7fs27sXnHtT5rH84oLlRAvUwaRw+okwRJY85gNQq+7xd3gZaVXE7BhgsJ6
AjKa0VajvwlGsqDQmk2VCckSdfhtOCcc5hYSoRXV9jXcDxjqLdsRRu6xulaOwRRZ
kRGlLCA/rRpyXeC5B6V9RRz2JKqXQbm8BvhVhQsPfmb/0/jnNuqZu6sYoE1zpJ2u
N/bAtpGjGikEaL0haJvNUmbAlhz3MEfpaRXOdjG6n8wvRMJOGuyP9zla+LdkPiVQ
z55piryZilOi6kOXOsFskzil+Rfv4+QXf5lVq7Ql6bzlUBtxGJrS6CGYaog9k0wK
l1EFHvdcqnJspFCS7wvLo/UAZGJw/dyGz5pGlztyyRCPhj9tvUjkxKOER5miX0/I
Kug7VfIN9tRN5jrtiz1VwBaIJJTgM9RvCDN72GRp6+esEdHJFvEEAMu0/iM4WrGe
lo4BeIajXJPIYLUIPqKZvDI3DeibL5X1RTplotEic4LaP56xxSaEhf8ZTgO34J/c
Z6DXqj0bOqeVMWCkaK7V+6Eo8eMfiSLu1YHswW7jXrc62uzGVcprMdYQfgfZZ03T
MrATldjEMLUoJoakErgIvm5WlXHr6YoozIMqnLwHi1hNf+sLYuxA0gFz9hWQFNyK
WBB5R8sNTBRfH3eBRbtp
=8e2q
-----END PGP SIGNATURE-----
--Apple-Mail=_FABC8C7D-1ACC-4D72-9CD5-873293ACC47D--
- Raw text -