X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f X-Recipient: geda-user AT delorie DOT com Date: Tue, 26 Feb 2019 17:35:14 +0100 (CET) From: Roland Lutz To: "Girvin Herr (gherrl AT fastmail DOT com) [via geda-user AT delorie DOT com]" Subject: Re: [geda-user] graphical not overriding netlister In-Reply-To: Message-ID: References: User-Agent: Alpine 2.20 (DEB 67 2015-01-07) MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset=US-ASCII 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 Hi Girvin, On Thu, 21 Feb 2019, Girvin Herr (gherrl AT fastmail DOT com) [via geda-user AT delorie DOT com] wrote: > It was my understanding that if "graphical=1" is used in an instantiated > symbol, that the tools will ignore that symbol. Apparently, from my > observation that is not quite true. Is there another way to disable a > symbol so that the tools ignore it, or what am I doing wrong with my use > of "graphical"? unfortunately, no, the tools won't ignore that symbol, and no, there is no other way to "disable" a symbol. There's a simple solution for your problem, though: update to the current "master" branch. The graphical=1 attribute means that the component is part of a separate "graphical" netlist that is relevant for netlisting in some ways but not in others. The typical use case would be a titleblock (which can have attributes, and these attributes are available to the netlister) or net annotations like "not connected". When refactoring the netlister, I changed the behavior regarding graphical components: they now aren't included in the default netlist any more unless the backend decides otherwise in order to avoid the exact situation you describe. Roland