X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f
X-Recipient: geda-user AT delorie DOT com
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type;
        bh=MHyfvFI3hnxMrnl7zOeF7kJB096E2cSvXt+uiTV8I8o=;
        b=kAV/69oh50DYDZlR004CTbdEc2+Ebu2NqME73sxeh2UM+9uv94yx0x/w0DdTMQ1PN3
         dO3u2od1DL6Ld65IxtcPL/r7vhkA2dffrG+aBxUuUdD2zDgu3PGIJ2zTjbTeq7C2z3Ng
         H4XgJzJnKS92VURAkzUoW2AHbV8kpAZnZh9jo2IB0GcMmYDiq1xxhBYHtFh8I9OkS/Hb
         OtrCcrkTjufbgGaL/oNjCKz1ZwSSnjZ/UZHtXzKflFeEtuzDdmPoBDIo7hA+aKi2aaRG
         qzNirUrR/bh40ER8nriBq9qiM3qo/eZ8/yTC+36p7cbA2z+CQVbfRV4yuMNzY4p4h/Ml
         fHrg==
MIME-Version: 1.0
X-Received: by 10.180.208.112 with SMTP id md16mr22000235wic.37.1421565198964;
 Sat, 17 Jan 2015 23:13:18 -0800 (PST)
In-Reply-To: <20150117222659.0CE0581A5EB7@turkos.aspodata.se>
References: <CALSZ9gp08b7L5HMesdT3yX-di-0PsqqjRA0b0RKGbc4FtOm6rQ AT mail DOT gmail DOT com>
	<20150117213351 DOT 106EE81A5EB7 AT turkos DOT aspodata DOT se>
	<CAOFvGD5+=KfJ=6m+96ASmDe9QZ1DeSiJoQAWXbBGww0H+3z85g AT mail DOT gmail DOT com>
	<CAOxVtSS9FVpgh1eYdj4tSr8LVkdp0=H8VVgxVAM=tYCqaAQY5g AT mail DOT gmail DOT com>
	<20150117222659 DOT 0CE0581A5EB7 AT turkos DOT aspodata DOT se>
Date: Sun, 18 Jan 2015 11:13:18 +0400
Message-ID: <CAOxVtSTADuYw==HnazDmNnuysOtL6pJk=vMCz4BV_5Xw6fPRQg@mail.gmail.com>
Subject: Re: [geda-user] HIDDEN PINS IN A SYMBOL
From: Sergey Alyoshin <alyoshin DOT s AT gmail DOT com>
To: geda-user AT delorie DOT com
Content-Type: text/plain; charset=UTF-8
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 Sun, Jan 18, 2015 at 1:26 AM,  <karl AT aspodata DOT se> wrote:
> Sergey Alyoshin:
>> On Sun, Jan 18, 2015 at 12:44 AM, Jason White
>> <whitewaterssoftwareinfo AT gmail DOT com> wrote:
>> > On Sat, Jan 17, 2015 at 4:33 PM,  <karl AT aspodata DOT se> wrote:
> ...
>> >>> How can I make the pin statements in the symbol that would allow 2 anode
>> >>> pins and 4 cathode pins?
>> >> Nothing stops you from overlap the pins, like the attached fp.
>> > Cool! I had never though of that.
>> Overlapped pins already connected with zero length net, so this should
>> not be done for N.C. pins. It would be convenient, if pinnumber can
>> have a list value, e.g. "2,7,8".
>
> If the pins are overlapping in the sym, the semantics must (?) be that
> they have a cu path internally, or ?

If some pins have cu path internally or not is not always specified in
documentation.

> If you have something that looks like one pin, shouldn't that iimply
> that regardless of which "sub-pin" you use, you get the same connection.
>
> If you have pinnumber=2,7,8 and connects a NC sym directly to that, do
> you want the NC sym be implicitly triplicated ?
>  What if you move the NC sym a little so there is a little short net,
> and then what if the net is connected to something else ?

Then the would be no red square on that single symbol
 pin with pinnumber list and you can see whey (pins in list) are
actually connected somehow.

> I think only meaningful semantic is if it looks like "one" pin, it
> should behave as if all "sub-pins" share the same cu-path internally.
>
> ///
>
> Now for the case of ic's with lot of NC pins, maybe just not drawing
> thoose pins in the sym is the solution. What do you think ?

It is confused for others, who is have a deal with such schematic, as
it looks like it may miss maybe something important.