X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f
X-Recipient: geda-user AT delorie DOT com
X-Injected-Via-Gmane: http://gmane.org/
To: geda-user AT delorie DOT com
From: Kai-Martin Knaak <knaak AT iqo DOT uni-hannover DOT de>
Subject: Re: [geda-user] gschem refactoring ideas  -- overall architecture document.
Date: Fri, 13 Feb 2015 22:46:03 +0100
Organization: Institut =?UTF-8?B?ZsO8cg==?= Quantenoptik
Lines: 57
Message-ID: <mblqsg$pth$1@ger.gmane.org>
References: <54DBDFF1 DOT 1010409 AT ecosensory DOT com> <FE92BD5F-0CB3-4CAE-B3BC-D63D22B579DA AT noqsi DOT com> <mbgul5$j8i$1 AT ger DOT gmane DOT org> <220C1787-45BF-459E-B217-29686DC25DF2 AT noqsi DOT com>
Mime-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
X-Complaints-To: usenet AT ger DOT gmane DOT org
X-Gmane-NNTP-Posting-Host: 130.75.103.107
User-Agent: KNode/4.14.1
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id t1DLcejS020111
Reply-To: geda-user AT delorie DOT com

John Doty wrote:

> On Feb 11, 2015, at 3:19 PM, Kai-Martin Knaak
> <knaak AT iqo DOT uni-hannover DOT de> wrote:
> 
>> A unambiguous sort of symbols on save would finally solve a still
>> standing issue you may remember: gnetlist behaves differently depending
>> on the order symbols were added.
> 
> I agree this is an annoyance.

It messes with components that are represented by more than one symbol. 
Consider an opamp which is represented by the usual  triangle and a 
separate box for the power supply. The power supply symbol contains the 
footprint attribute.
This is good style and recommended for clarity. It reduces the clutter but 
still shows all the pins. 

The netlister looks only at the first symbol of a group when it determines 
the footprint. If the power rectangle was placed after the triangle, the 
netlister thinks, acts like this is a component without a footprint. This 
frequently leads to confusion among students I teach the fundamentals of 
geda.


> However, take account of the problem of
> filled graphics, where one may manipulate that order to get the
> appearance you want.

Fair enough.
Applications like inkscape or xfig provide user accessible functions to 
raise or lower a selected item. So order is relevant for the graphical 
representation. But it certainly should not matter to the netlist.
With that in mind, a sort should take place on read input of the 
netlister. 

---<)kaimartin(>---
-- 
Kai-Martin Knaak                                  tel: +49-511-762-2895
Universität Hannover, Inst. für Quantenoptik      fax: +49-511-762-2211	
Welfengarten 1, 30167 Hannover           http://www.iqo.uni-hannover.de
GPG key:    http://pgp.mit.edu:11371/pks/lookup?search=Knaak+kmk&op=get