X-Authentication-Warning:	delorie.com: mail set sender to geda-user-bounces using -f
X-Recipient:	geda-user AT delorie DOT com
X-TCPREMOTEIP:	207.224.51.38
X-Authenticated-UID:	jpd AT noqsi DOT com
Mime-Version:	1.0 (Mac OS X Mail 7.3 \(1878.6\))
Subject:	Re: [geda-user] Netnames on all connected segments
From:	John Doty <jpd AT noqsi DOT com>
In-Reply-To:	<20150912154939.6ac1821b810f21e649500530@gmail.com>
Date:	Sat, 12 Sep 2015 09:13:12 -0600
Message-Id:	<9A64E94A-3E27-41BD-A4D3-8A30E63D3251@noqsi.com>
References:	<20150912002643 DOT d476ca384a4a11ddda3b3a52 AT gmail DOT com> <6410018E-5F28-4960-815F-19862EEB7A9A AT noqsi DOT com> <20150912093138 DOT d6c2bcc54026a0af677f746e AT gmail DOT com> <BAE0ADA0-6D34-4CBC-B5C0-BA959D85B0FA AT noqsi DOT com> <20150912154939 DOT 6ac1821b810f21e649500530 AT gmail DOT com>
To:	geda-user AT delorie DOT com
X-Mailer:	Apple Mail (2.1878.6)
X-MIME-Autoconverted:	from quoted-printable to 8bit by delorie.com id t8CFDMp7008689
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

On Sep 12, 2015, at 7:49 AM, Nicklas Karlsson (nicklas DOT karlsson17 AT gmail DOT com) [via geda-user AT delorie DOT com] <geda-user AT delorie DOT com> wrote:

>>>>> Would it be hard ta add the netname all connected segments then it is added or changed?
>>>>> 
>>>> 
>>>> How would you undo a short circuit (an especially likely event with magnetic net mode enabled)?
>>> 
>>> Actually I have no idea. What I want is all segments of the net have the netname attribute set and to the same value. Then looking into the save *.sch the netname attribute is assigned to one of the lines.
>>> 
>>> Do gschem know about nets?
>> 
>> A little knowledge of nets has crept into gschem in recent years, and that has caused some troubles See, for example, https://bugs.launchpad.net/geda/+bug/1014160.
>> 
>>> Or only draw nice junctions and let gnetlist generate the netlist?
>>> 
>> 
>> Mostly yes. Gnetlist slows down a lot on big designs because it uses an inefficient algorithm to search for junctions.
> 
> It is able to mark a net then double clicked but only on a single page and does not follow the hierarchy.

Yes, and that makes it hard to “clean up” a box selection that has grabbed a segment you don’t want. I therefore have (net-selection-mode "disabled”) in my ~/.gEDA/gschemrc. The trend to complicating simple mouse actions in gschem is unwelcome, but at least you can turn this one off.

The other thing that it does is decorate open net segment ends differently based on heuristics that include connections to other segments. I really dislike this feature. It’s supposed to tell the user when a dangling net is OK, but it’s not reliable and therefore confusing.

>  If it is able to mark them I guess the same code or algorithm could be reused to change the net name on all segments.
> 
> As is now the connections are saved as lines and netlist figure where they are connected?
> 

Kind of. Net segment objects are not the same as line objects, but yes, they are just simple graphics.

Think of gschem as a graphical editor. An editor’s job is syntactic, not semantic. Think of gnetlist as a topology compiler, taking the graphical source code and compiling it to the more abstract netlist.

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

- Raw text -