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=sbcglobal.net; s=s2048; t=1449708074; bh=gHCNuldJ4uCdw0mpvSCYBbak4ms/PIirFc30CI9P8cE=; h=Subject:From:In-Reply-To:Date:References:To:From:Subject; b=QEfoOfJ1xg+b+8XMHAAQrCv8CsET7ksNNmyWtZMhB9XBLlRvzwuZ1vUjuhhGmS7FwJMBTcztItuXefKBaLw4j4dyqQ68T27IIFTZL1tlFj9/BYoL/bvdzJYpSYS/02h1EJv7ty3w6xIKBjTQjS5w7VjysNMTAqVvwO3XkLGL9rSLzme5MoZN0TO5KySx0SDGNhSuT51lhNg/jb+RkrJ7IRI/PtE6+ldgHlvg49Nar1F6EF3fScPskdX8mMf69x9caYFs3TOmsLj1GJ58SUMWkg1uIQZ2Jmp4E75W8uzl//jLbFz1DRa/TZvuo96yPA3mHpXNdkiITxsY2ydbgYXAaQ==
X-Yahoo-Newman-Id:	932226 DOT 89834 DOT bm AT smtp210 DOT mail DOT gq1 DOT yahoo DOT com
X-Yahoo-Newman-Property:	ymail-3
X-YMail-OSG:	4I420ksVM1ls7CW.F.NPSaQ4kqkPcerH.nw20uSOWDwA3ek
	dgXMbO1ByuTODw_dpLVrW.2ERChd6.QPoHOmID2osCCEOYhYiskJZj9qmWkx
	6Z4dEU2VclF2kRZ0Dk4CMogkT5Z0aJ6uDtRRea1olww5kduhfDp1gY_UlZjQ
	hiDuPpFrc.GMCQ1HVMF.eBnoUQpGYIuOH5rAmIgFoDXzzZmnwrsIU1miK0.s
	l_W1NMEK7To3VS1lncfvBFKFMmz9m8_ZqWd.fwVNs.sqodEVhA2mbiNZhHlt
	3ocshk6c4ojTlB17UMO92nhYkBR8gMe4dnlWJNsnFSK0J7R_LrG9sPUhwBgv
	HfWzcNIPU68_LrhOhXQcrJrcCgyiEHx3mXht.N1sBIACJV14cgNKep2pqV9B
	d2MPlfa9m5SVSqBJegS3Hy4Xrdx9drj13K208hj2ESj4vag3UAT5n_6Vqyja
	BcJEUwRqFLKTY.dqk0elS6fhdEOILYN1eGcP_Qw6fcgpo4EIni4JPffYlF.W
	pRcBUUgPzYs2.ZUowkTIPBoWNsehVkg5FNjh8bQYPHfIBVU6SQw--
X-Yahoo-SMTP:	b8jVkbOswBAqZ4BhECp7nxPJUfTGEnEGv_G4qgQeZMeAbA--
Mime-Version:	1.0 (Mac OS X Mail 8.2 \(2104\))
Subject:	Re: [geda-user] gsch2pcb after refdes-renum? (If implemented syncronization detail)
From:	"Edward Hennessy (ehennes AT sbcglobal DOT net) [via geda-user AT delorie DOT com]" <geda-user AT delorie DOT com>
In-Reply-To:	<86263A11-92E5-402B-95E5-5228B6FE1C65@noqsi.com>
Date:	Wed, 9 Dec 2015 16:41:12 -0800
Message-Id:	<76D5DA43-C966-4881-AA72-B7BEEA74E1AA@sbcglobal.net>
References:	<56658683 DOT 401 AT envinsci DOT co DOT uk> <CALT8Ef4=tMf=WmjYmp-2B3rN0SBmoqF5RkCoWZEm=+2hTBTENA AT mail DOT gmail DOT com> <20151207153821 DOT c2ac19e6f24b1776a3595e4a AT gmail DOT com> <CD4C755E-8E00-427D-909C-3F762A038844 AT gmail DOT com> <20151208091411 DOT c8968b0bedb705765529176c AT gmail DOT com> <B2F4DA99-3254-4C97-A408-854445A09C21 AT noqsi DOT com> <201512081819 DOT tB8IJBrt022764 AT envy DOT delorie DOT com> <20151208205451 DOT bb2478f8722e1a885822689d AT gmail DOT com> <201512082019 DOT tB8KJOlP030874 AT envy DOT delorie DOT com> <72D9CDFB-BB8D-4A81-9712-2D58F802B900 AT sbcglobal DOT net> <86263A11-92E5-402B-95E5-5228B6FE1C65 AT noqsi DOT com>
To:	"geda-user AT delorie DOT com" <geda-user AT delorie DOT com>
X-Mailer:	Apple Mail (2.2104)
X-MIME-Autoconverted:	from quoted-printable to 8bit by delorie.com id tBA0fLvw030612
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

> On Dec 8, 2015, at 11:01 PM, John Doty <jpd AT noqsi DOT com> wrote:
> 
>> Perhaps gschem could assign an artificial or surrogate key to the symbol and store it in an attribute.
> 
> And then what happens when you make a copy?

For an artificial or surrogate key that identifies an instance of a symbol, something like:

COPY
~~~~
1. Copy objects to buffer
2. Assign a new identifier to symbols in the buffer

CUT
~~~
1. Copy objects to buffer
2. Remove objects from schematic

PASTE
~~~~~
1. Copy objects to schematic
2. Assign a new identifier to symbols in the buffer

It would also be nice to have some surrogate key, that could be either artificial or natural to identify a part. For example, if there is more than one symbol to represent a 74HCT00, a refdes renumbering program could identify that all the instances belong to the same part, and assign slots properly. A natural key could be a company part number, but many don’t create company part numbers, so an artificial key may be better in this case.

Ed

- Raw text -