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=gmail.com; s=20120113;
        h=date:from:to:subject:message-id:in-reply-to:references:mime-version
         :content-type:content-transfer-encoding;
        bh=mtujkzqB7FjwZAc4AK5gw/1xpOj5/nCA4KPA85vP6nQ=;
        b=KgJ9DrzNsjOTWDQBOhuLOgSMVuIi0BgyAgCQqmrpBrzJc+JaZNBYxgrjxEXRBne1js
         gjhisHJBH2a7RmKrgfitz/iFcB24eMo99E4eyGw42FoyMquaGtIh7x2ItcVJJauxCIrN
         LO3khdA4304USpKUnfp6gYnOyFCtYcEReSFfxKPqymuMzM9bxlLmhkhbR/Gqbj2BXfNX
         2touY6lXwyeVth0LfgarMZBEc3czgXzJF5q5UVLxl3+Q+xef7jlgNGUCtZnYjmSNHC5i
         7h226kTKo+/udQ1EzeoTKKAJ7gBHQTjNStlUBVyMSbzdFZDB5s7NlpBxdyK1bkJRdA/A
         VwLw==
X-Received: by 10.112.126.164 with SMTP id mz4mr19892787lbb.70.1451762370407;
        Sat, 02 Jan 2016 11:19:30 -0800 (PST)
Date: Sat, 2 Jan 2016 20:19:28 +0100
From: "Nicklas Karlsson (nicklas DOT karlsson17 AT gmail DOT com) [via geda-user AT delorie DOT com]" <geda-user AT delorie DOT com>
To: geda-user AT delorie DOT com
Subject: Re: [geda-user] ideas on slotting and mechanisms for
 grouping/associating heterogenous symbols.
Message-Id: <20160102201928.7088e064ac2f7ca3c6d2070b@gmail.com>
In-Reply-To: <201601021816.u02IGHCC021127@envy.delorie.com>
References: <CAM2RGhS4L-ch6FEcLtdSt0vA0BdQZvq+AuFDP+9ea7Ftd=AALg AT mail DOT gmail DOT com>
	<8444F816-17CE-4A56-A982-4A60DEDA72B8 AT noqsi DOT com>
	<alpine DOT DEB DOT 2 DOT 00 DOT 1512300544550 DOT 9035 AT igor2priv>
	<87FC7D4C-157A-499E-8B93-97653D6A7C68 AT noqsi DOT com>
	<alpine DOT DEB DOT 2 DOT 11 DOT 1601012231450 DOT 1728 AT newt>
	<AE52C1DB-01A3-43FA-AE8E-68AD33F37180 AT noqsi DOT com>
	<624E6A69-62CE-4FCB-9D44-9FDF036254A3 AT sbcglobal DOT net>
	<56880043 DOT 7040003 AT ecosensory DOT com>
	<20160102182739 DOT 5d195829880cf75768ae0a82 AT gmail DOT com>
	<201601021755 DOT u02HtOWs020325 AT envy DOT delorie DOT com>
	<20160102191018 DOT 5e68c0c4ecc70a49bd9998f6 AT gmail DOT com>
	<201601021816 DOT u02IGHCC021127 AT envy DOT delorie DOT com>
X-Mailer: Sylpheed 3.5.0beta1 (GTK+ 2.24.25; x86_64-pc-linux-gnu)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
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

On Sat, 2 Jan 2016 13:16:17 -0500
DJ Delorie <dj AT delorie DOT com> wrote:

> 
> > That's a collision. Ideally all symbols ending up in the same
> > footprint should have the same refdes. I would say the naming scheme
> > for hierarchy does not fit for this case and I can't figure out how
> > to get a good solution.
> 
> Consider, for example, you have eight NAND gates in your circuit, in
> two quad packages.  You decide that swapping two gates across packages
> would make sense for the layout.  However, this changes the refdes for
> those two gates, so you have to manually pre-swap them in the
> schematic.
> 
> Should this be something you can do in the layout program?
> 
> If so, how do you specify "that gate" in the schematic when you want
> to make an as-built?

I would say normally refdes is used because it is rather simple to understand. It would also be possible to override and say they are in same swapping group even though refdes is different but in such case back annotate is needed to get correct refdes. Maybe a refdes group?


Nicklas Karlsson