X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f X-Recipient: geda-user AT delorie DOT com Date: Tue, 17 Jul 2012 16:01:13 -0700 From: Colin D Bennett To: geda-user AT delorie DOT com Subject: Re: [geda-user] gnetlist: allow net= attributes without a pin number Message-ID: <20120717160113.2caabc78@svelte> In-Reply-To: <000301cd644d$75518ab0$5ff4a010$@de> References: <000301cd644d$75518ab0$5ff4a010$@de> X-Mailer: Claws Mail 3.8.0 (GTK+ 2.24.10; x86_64-pc-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - gator297.hostgator.com X-AntiAbuse: Original Domain - delorie.com X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - gibibit.com X-BWhitelist: no X-Source: X-Source-Args: X-Source-Dir: X-Source-Sender: (svelte) [65.61.115.34]:38430 X-Source-Auth: colin AT gibibit DOT com X-Email-Count: 1 X-Source-Cap: c2t5bGVuO3NreWxlbjtnYXRvcjI5Ny5ob3N0Z2F0b3IuY29t 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 Tue, 17 Jul 2012 20:53:29 +0200 "Markus" wrote: > Hello, > > in the geda-developers team mailing lists there is an very > interesting patch.: > (actually, I would like to have it very much in the next > release ;-) > > https://lists.launchpad.net/geda-developers/msg00079.html > > Is there a chance, that it get somehow integrated? Yes, please do! This feature would allow me to avoid the ":1" on all my pin/port symbols in my schematics. It's not just ugly, it makes it really hard to read the correct net name especially in net names that end with numbers like "LED12:1" or "P2_3:1". Currently I use a workaround where the 'net=P2_3:1' attribute is hidden on my pin symbol, and I use an extra, visible 'value=P2_3' attribute. But this is error-prone in that I could screw up and the net= and value= attributes might disagree--causing the PCB to be wrong, and worst of all you can't see the error on the schematic itself so no amount of plain visual review will find it. (only extensive and tedious checks of all pins, and using extreme care) Regards, Colin