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=sbcglobal.net; s=s2048; t=1438549833; bh=YEmH+2HDpXTie09HQAiYtM+2jlnmw3oNKfWMH1xvcRs=; h=Subject:From:In-Reply-To:Date:References:To:From:Subject; b=B54prija8myIhMqcjxscbKjhD8Rm/wJ/0crmUFU9koOb96nnS56qsxdPkHgZe26gPwiV+aYrqx0ohoTpIl/sFj8IO/lnTxrBnbkEouQFAx7VwZIziZc/yIHlrMvl+QYZdNsPcpLV0XVP5R0qhadhHIzAeHv2k8K2UqdjTid1Uxdx0c9lWMQ4+cq4HJJtjvfoas8Tiuud1eACVDOevpoZtg0RsZuErhrbrLEv7P6rFBDQ+17/zrmBLzIu95Ge+nhYyiDDAd8i2T4WGA7NJRDB3ERVG+pvr530qao7lGG5mAi2IZNkuIshx2lympPlfU2q8MKm43ahe1fRXKK35zchrA==
X-Yahoo-Newman-Id: 202479 DOT 32827 DOT bm AT smtp229 DOT mail DOT gq1 DOT yahoo DOT com
X-Yahoo-Newman-Property: ymail-3
X-YMail-OSG: qxV7C70VM1lQZp_eQYc6MtPqER3kTA2I1ksW9slj0ip7ypS
 WP9lIbn6Hcrh5.Hi2iVmw3DvICPz1GL7MjsksQXnSPbir9k_EKwTlqge5NNJ
 kkRvfeI2MeOVXiH2g_DDcSRiB30_BqNtVHDHtsTFJwjwQS20PxwR.a73V2Q7
 tM1wawOUAmwqumER.rxi6ByYW1GuEqK9Q2KC9jMx8Rtl4pl7rrZK3TIAWImh
 .OKVuOkD09NJ25hRYFtGnFrLvUo7ZACAU3szfvcLYPzIUEClp0EgcOuKW_yH
 eEpfkFrm3zuXCqSoW0n0FBuj880K5Q8rtIOrc.l1PjCnOF5iI9.3UZLa2Nhs
 BaK0QR9yNFcGzW5JI3GXvwAfZ701RmswPBDWMlYFtE96cfcKBPX_KxgWU7Vb
 FckXCRjuKMxlVCLViTmYa.NpmIDam5rabIvISEyiGXteY4IIB2sbdwmUdfo1
 b0ySE8KIrPxXr6uuaZASqfPkbI5CZe0EC9sEv5JJQkjGJywRgx1lZ.vpDu2x
 HhFQvoJFoVSUdfQ92EAUVYpKxW2_RkELXXhhKx2Up
X-Yahoo-SMTP: b8jVkbOswBAqZ4BhECp7nxPJUfTGEnEGv_G4qgQeZMeAbA--
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2102\))
Subject: Re: [geda-user] Improved Find
From: "Edward Hennessy (ehennes AT sbcglobal DOT net) [via geda-user AT delorie DOT com]" <geda-user AT delorie DOT com>
In-Reply-To: <BDB5FA15-D1D3-4BA4-AEDC-092D94A0E72D@noqsi.com>
Date: Sun, 2 Aug 2015 14:10:30 -0700
Message-Id: <5E2BB4CD-4E81-45DE-80E0-5CAFE9D85ECC@sbcglobal.net>
References: <FF2A0FBC-75B1-4A3E-9588-CD3DB7CC448A AT sbcglobal DOT net> <5329D15C-0713-4919-8205-AC474BAC5652 AT noqsi DOT com> <CAC4O8c_bRzahs66fCYsuNggvuwy0-JxGbTu8EJsGwaeSVB8G-Q AT mail DOT gmail DOT com> <FFA87469-7432-49C7-8AF5-153C41DFE78F AT sbcglobal DOT net> <CAC4O8c9241Z8A6-kKTQM6f=CTxtTU_-Dmj9uMOqqmp68_OuZxg AT mail DOT gmail DOT com> <BC57B367-8548-4947-B29C-A69378423BA8 AT noqsi DOT com> <631C0577-E61D-40BC-B200-96BA897092E6 AT sbcglobal DOT net> <CAOFvGD5mKEWO9oJpK2HPvLLgAPGB_2YW2vq6hSdqSF-Wkz0TuA AT mail DOT gmail DOT com> <BDB5FA15-D1D3-4BA4-AEDC-092D94A0E72D AT noqsi DOT com>
To: "geda-user AT delorie DOT com" <geda-user AT delorie DOT com>
X-Mailer: Apple Mail (2.2102)
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id t72LAbhq029082
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 Aug 2, 2015, at 10:12 AM, John Doty <jpd AT noqsi DOT com> wrote:
> 
> Perhaps I’m misunderstanding, but it appears that you are assuming that the pages open in gschem represent some sort of coherent, organized design. In real life, they don’t: the coherence eventually emerges from what you’re doing with the pages, but it’s not necessarily present in the set of pages you have open.

I've only used flat for schematic designs, but it is becoming apparent:

- The page manager can only make a best guess to the hierarchy of a design. If a page isn’t loaded, it won’t show the complete story.

- A schematic can have multiple parents, but gschem doesn’t have the functionality to track more than one parent. And this variable only stores the most recent “up.”

It seems to me:

- That the page manager shouldn’t try and track the hierarchy. It should have a flat list of all the pages that are loaded. If hierarchy is tracked, it should be done somewhere outside gschem.

- The page manager could possibly show one level more, but just the dependent filenames.

- The push schematic menu item should expand into a list of all the source files that could be descended into for that symbol.

- The “up” should not be stored in the schematic page data structure. It is associated with the view and stored as a stack. The view would push and pop pages on the stack as the user pushes symbols/schematics.

Ideas?

Ed