X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f X-Recipient: geda-user AT delorie DOT com Date: Sun, 29 Jul 2018 22:38:07 +0200 (CEST) From: Roland Lutz To: "John Griessen (john AT ecosensory DOT com) [via geda-user AT delorie DOT com]" Subject: Re: [geda-user] Hierarchy in gschem - how? In-Reply-To: Message-ID: References: <20180728125649 DOT GA22385 AT esprimo> <20180728140448 DOT GA22943 AT esprimo> <20180728190412 DOT GA27016 AT esprimo> User-Agent: Alpine 2.20 (DEB 67 2015-01-07) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed 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 Sat, 28 Jul 2018, John Griessen (john AT ecosensory DOT com) [via geda-user AT delorie DOT com] wrote: > What he meant was, if not using repeated elements of layout, you can > just connect between sheets of a schematic with named nets. No, what I meant was: all these conventions around hierarchy are only relevant for netlist generation. If you are not intending to generate a netlist from the schematics (i.e., export to a PCB or simulation tool or similar), then only the visible graphics matter; in this case, gschem is basically a drawing program to you, and you can draw whatever you want. You are still free to use source= attributes to make navigation between the schematic pages easier, but that's just a convenience bonus.