X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f
X-Recipient: geda-user AT delorie DOT com
X-TCPREMOTEIP: 63.119.35.194
X-Authenticated-UID: jpd AT noqsi DOT com
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
Subject: Re: [geda-user] Improved Find
From: John Doty <jpd AT noqsi DOT com>
In-Reply-To: <20150802212228.GA17264@visitor2.iram.es>
Date: Sun, 2 Aug 2015 19:22:56 -0400
Message-Id: <3DF2CEB4-A143-4C48-8DB9-C303603A75A1@noqsi.com>
References: <FF2A0FBC-75B1-4A3E-9588-CD3DB7CC448A AT sbcglobal DOT net> <5329D15C-0713-4919-8205-AC474BAC5652 AT noqsi DOT com> <CAC4O8c_bRzahs66fCYsuNggvuwy0-JxGbTu8EJsGwaeSVB8G-Q AT mail DOT gmail DOT com> <FFA87469-7432-49C7-8AF5-153C41DFE78F AT sbcglobal DOT net> <CAC4O8c9241Z8A6-kKTQM6f=CTxtTU_-Dmj9uMOqqmp68_OuZxg AT mail DOT gmail DOT com> <BC57B367-8548-4947-B29C-A69378423BA8 AT noqsi DOT com> <631C0577-E61D-40BC-B200-96BA897092E6 AT sbcglobal DOT net> <DAC3E2ED-AB1E-42C7-AA0B-78853F31A95A AT noqsi DOT com> <20150802172151 DOT 45DD480395AE AT turkos DOT aspodata DOT se> <EEDC318A-1649-4FCD-B80C-7D58F89668BA AT noqsi DOT com> <20150802212228 DOT GA17264 AT visitor2 DOT iram DOT es>
To: geda-user AT delorie DOT com
X-Mailer: Apple Mail (2.1878.6)
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id t72NN312006533
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 Aug 2, 2015, at 5:22 PM, Gabriel Paubert (paubert AT iram DOT es) [via geda-user AT delorie DOT com] <geda-user AT delorie DOT com> wrote:

> I always had the impression that the attribute handling rules are too 
> complex;

Yes, although part of the problem is just confusing terminology. We could use the terms “override default” and “restore default” for promoting and deleting instance attributes. That would make the existing functionality clearer, I think.

> it would be much simpler to say that all attributes are promoted 

Ah, but that causes chaos for those of us who sometimes use “heavy” symbols. You often want to be able to edit the symbol once to change attributes for all of its instances. About five years ago somebody changed the default attribute promotion rules to promote more things, and I still haven’t completely straightened out the resulting mess.

> and the symbol attributes are only sensible initial default values, which 
> are always ignored when processing the schematics (generating a netlist 
> being the most common example).

Promoting *nothing* unless you want to override it works better with heavy symbols.

> 
> BTW, doesn't the net attribute have similar problems: many 74xx symbols
> have net=VCC:14 (or 16, or 20) and net=GND:7 (or 8, or 10).

Yes, I forgot about that one.

John Doty              Noqsi Aerospace, Ltd.
http://www.noqsi.com/
jpd AT noqsi DOT com