X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f X-Recipient: geda-user AT delorie DOT com X-Original-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to; bh=ZRYV5TkRe4Brnq4jiK0FdRy6+cCEnHGmVoLEXCyiqLY=; b=iQk6E7VUsVuWx0hamtYq4BCcI9Y2Z3gCq70UQsElw/lvEtuWijmagbKfrYMSw3TdlB zR6+aw/63YdHRS7FSK2TdpoDkaWoEspeNwAfMETWQriEgXBwVH6/lYAM+O8Xon37MZFB N9hnvsOO6AbGtY68pYLvR2pDK0C3GgPB09T9gEuXuUYOzh5yBrS/PJx8NU9w1Ivjkip7 X8ldlBo1rs2Y3DhnUSVCFRgve1WmXQC5TDCLM8CwjhvfqNrJHcf39cX1nmGkkIl0+Dd9 IKAc4wBKoWmQs5igwY8qo0U5xciPWtrgGQ/BZ65lw8EaKvSoXvF2kqOGcB7NDomI4AL2 1mjg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to; bh=ZRYV5TkRe4Brnq4jiK0FdRy6+cCEnHGmVoLEXCyiqLY=; b=Of6abyw8/Ag2eEdwBk6mkipxeXg8q02HFhd1sH5nPUtVrDTLBhVRe//OaFPy7LE6IF jcm9Mrsl5ebVROOzAHiSJFE13nsXVGSoJ2tmYma7PagRrMLCSfMv/mjPxhXTRgyZW7tp K6cBd4p0CehU/w5/EA59DqDmOAAzjP/cjqUZ2lNxRNbiu2zmySo0/kCKAkTfpDP1D1LF 2PliYI1l87pUXaJeDJcYoP8hNnnQaMAYRo0YPQoBOR9Ucyi6w2lp6l0d8D4JmBBV5KFH 0C3QT6Iaxdu91ij+rUAX8dkevwX0EfwNzES+pZRLrJsw1l1rtv8bvFXpPBjiu15DyzpK r3Sw== X-Gm-Message-State: AMke39meGurv+rbIxjmWWOpmnlUYyjyJGlpRpvrZjQiolRvOlsQxJJUPUP23rZZ/MWOsp6YfTORiAvnRvvVhRA== X-Received: by 10.237.37.165 with SMTP id x34mr11852227qtc.218.1486806365543; Sat, 11 Feb 2017 01:46:05 -0800 (PST) MIME-Version: 1.0 In-Reply-To: References: <95e469bb-5572-fa1d-0c18-ed5abadd10cf AT ecosensory DOT com> <89b42141-9448-1c52-f4be-b4cc41ed7091 AT ecosensory DOT com> From: "Peter Clifton (petercjclifton AT googlemail DOT com) [via geda-user AT delorie DOT com]" Date: Sat, 11 Feb 2017 09:46:04 +0000 Message-ID: Subject: Re: [geda-user] gschem gnetlist bug/feature To: gEDA User Mailing List Content-Type: multipart/alternative; boundary=001a113d7ef644a79b05483e153a 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 --001a113d7ef644a79b05483e153a Content-Type: text/plain; charset=UTF-8 On 10 Feb 2017 22:18, "Roland Lutz" wrote: In master, setting a netname= attribute on a symbol doesn't work. Nor should it.. netname attributes name net objects (and must be attached to net objects). I hope this hasn't changed. If you want to add a power symbol purely for decoration, use a symbol without a net= attribute and set graphical=1. Otherwise (even when setting graphical=1 on a regular power symbol) the net will be connected to Vcc, or whatever net name the power symbol specifies. That seems somewhat counter to my recollection. I thought graphical=1 caused a symbol to be ignored completely? (Has this changed, or my recollection faulty?) If you want to create a power symbol which can be used for any custom net name, you could use a net=xxx:1 attribute and set it to show value only (but it would read xxx:1 instead of xxx This is how I do it, but if you care about the :1, you can hide the net= attribute entirely and add visible text (or a label=... attribute). I personally prefer leaving the :1 if it is defined in the schematic, not a custom symbol - as having two attributes, one visible, one not - which might accidentally be out of sync rather suggests possibility of errors creeping in. --you could use the experimental branch which allows you to set netname=xxx on the power symbol to remove the need for the :1 suffix). Which experimental branch is that? This is something which back when I was last working on geda-gaf (some years ago), we always strongly resisted that exact change - as it overloads the meaning of that attribute in a way which requires special casing, and only "helps" a tiny use case (the rendered text). We never felt the supposed benefit justified the unclean (slightly inconsistent) behaviour. Fwiw, we also resisted the proposal to have net= default to adding an implicit ":1" if not specified, or diving into the symbol definition to check if there is only one pin, and see what it is called. libgeda needs fewer inconsistent behaviours and hard coded special cases, not more! Peter Clifton --001a113d7ef644a79b05483e153a Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable


On 10 Feb 2017 22:18, "Roland Lutz" <rlutz AT hedmen DOT org> wrote:

In master, setting a netname=3D attribute on a symbol doesn't work.
=

Nor should it.. netname attributes name net objects (and must be attached= to net objects). I hope this hasn't changed.
If you want to add a power symbol purely for decoration, use a symbol witho= ut a net=3D attribute and set graphical=3D1.=C2=A0 Otherwise (even when set= ting graphical=3D1 on a regular power symbol) the net will be connected to = Vcc, or whatever net name the power symbol specifies.

That seems somew= hat counter to my recollection. I thought graphical=3D1 caused a symbol to = be ignored completely? (Has this changed, or my recollection faulty?)
=

If you want to create a power symbol which can be used for any custom net n= ame, you could use a net=3Dxxx:1 attribute and set it to show value only (b= ut it would read xxx:1 instead of xxx

This is how I do it, but if you care= about the :1, you can hide the net=3D attribute entirely and add visible t= ext (or a label=3D... attribute). I personally prefer leaving the :1 if it = is defined in the schematic, not a custom symbol - as having two attributes= , one visible, one not - which might accidentally be out of sync rather sug= gests possibility of errors creeping in.

<= div dir=3D"auto">
--you could use the experimental branch = which allows you to set netname=3Dxxx on the power symbol to remove the nee= d for the :1 suffix).

<= /div>
Which experimental branch is that?

This is something which back when I was l= ast working on geda-gaf (some years ago), we always strongly resisted that = exact change - as it overloads the meaning of that attribute in a way which= requires special casing, and only "helps" a tiny use case (the r= endered text). We never felt the supposed benefit justified the unclean (sl= ightly inconsistent) behaviour.

Fwiw, we also resisted the proposal to have net=3D default to add= ing an implicit ":1" if not specified, or diving into the symbol = definition to check if there is only one pin, and see what it is called. li= bgeda needs fewer inconsistent behaviours and hard coded special cases, not= more!

Peter Clifton
--001a113d7ef644a79b05483e153a--