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=5QxiPLb7NvaBDCD98QWnjtNMFWPhapIB3zTQ/YZvNKc=;
        b=znCIyKLqMg95tVS3Ie/+CfB7hWYTvD15zz1NRjeDU8F27s9RSoqr0M5SN/hiw7i9hA
         2KXa2mpXR9ptFE8AFlBw57EYPZM+XGZpP2jlntiSz0qOuhFzb78M7eGqGLYUAin1fvZ7
         fq9awY68wmWOpZmp9dQM2A3boVdqPyE5TFiYMIYHJjJsUgzTDarN/mdzNDNgS8uZ34Ip
         MMN/j3/AUIRKM4yB2j1FjjwBDj4p0K59gQqT4aOUmJgId/uypP0X/kPPUNGJgUswxnlk
         BI/9o7lo6Sf6fjNtti1CI27zIpJma3E0BxtiBjcSV1llXeFugS6WjRRS0q061NBuDwG8
         DQNw==
X-Received: by 10.112.73.69 with SMTP id j5mr19622833lbv.124.1451838180298;
        Sun, 03 Jan 2016 08:23:00 -0800 (PST)
Date: Sun, 3 Jan 2016 17:22:54 +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: <20160103172254.ec64cc4e27ac022aecf16968@gmail.com>
In-Reply-To: <CAC4O8c96LrdatY_g6f_Hh28C89m0ixnaP8tenJ40kp7tEy__RQ@mail.gmail.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>
	<20160102201928 DOT 7088e064ac2f7ca3c6d2070b AT gmail DOT com>
	<201601021921 DOT u02JLAjV023233 AT envy DOT delorie DOT com>
	<73498CB4-2C0D-4033-928B-A3AB62088E72 AT noqsi DOT com>
	<CAC4O8c96LrdatY_g6f_Hh28C89m0ixnaP8tenJ40kp7tEy__RQ AT mail DOT gmail 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

> > > It would be trivial to say "use U1a and U1b" - now they're unique but
> > > still indicate grouping.
> > >
> >
> > Yes. Have unique refdes per slot in the source, unique refdes per package
> > in the as-built.
> >
> 
> But isn't this overloading refdes values with magical non-obvious meaning?
> If it's already there and well documented fine, but otherwise how is it
> better than a separate attribute with a meaningful name?
> 
> Britton

Because they normally belong to the same footprint and should have the same refdes anyway.

I however think there will be a need to override default scheme with same refdes with a second attribute for some cases, in particular swap between several components. If swapping is allowed between components this second attribute need to be unique for the whole schematic which make it a little bit more cumbersome to use.


Nicklas Karlsson