X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f
X-Recipient: geda-user AT delorie DOT com
Date: Wed, 30 Jan 2019 16:16:22 +0100 (CET)
From: Roland Lutz <rlutz AT hedmen DOT org>
To: "Girvin Herr (gherrl AT fastmail DOT com) [via geda-user AT delorie DOT com]" <geda-user AT delorie DOT com>
Subject: Re: [geda-user] Refdes bug or Master Attribute Document on the Wiki
 needs update.
In-Reply-To: <alpine.DEB.2.00.1901301448260.21900@igor2priv>
Message-ID: <alpine.DEB.2.20.1901301557210.3182@nimbus>
References: <9ed059c0-f3c5-1482-169b-f8f1119f3208 AT fastmail DOT com> <alpine DOT DEB DOT 2 DOT 20 DOT 1901301419360 DOT 1543 AT nimbus> <alpine DOT DEB DOT 2 DOT 00 DOT 1901301448260 DOT 21900 AT igor2priv>
User-Agent: Alpine 2.20 (DEB 67 2015-01-07)
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII; format=flowed
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 Wed, 30 Jan 2019, gedau AT igor2 DOT repo DOT hu wrote:
> In some systems this is how you do slotting. Each slot is 
> <refdes>[a..z]. I haven't used such system, but I have seen this 
> convention on schematics produced with those systems.

With gEDA/gaf, this wouldn't work.  You'd either have to define separate 
symbols for each slot, or use gEDA/gaf's slotting mechanism and set slot=1,
slot=2 etc. on each component to change its pin mapping to a given slot.

If you have defined the slot number in slot= anyway, why would you want to
duplicate it in the refdes?  (This is a serious question.)