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=gmail.com; s=20120113;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to;
        bh=1gst8wLNhuRkPheZ8KuCI3b7Sj15ntjEdpHpSCsQIwU=;
        b=LEYa07x51qFIieCYjv5hLdxOuEZJB751N3dgtxTulMjEARiaslsHJA/BCDAZLmWn3H
         BV8X9OuxeYTo03SlwrnrnmdpAfx0O8u4BNiDhlzffNyIXTM4V+R45pBKIrlgiTSI+QuJ
         GDMX7Bdz7STs88UVXceWeCH4AF7Koy2bfqHqEuw53qK2TQXuLzt2vGjlzfSdTdYqi0ic
         xiDxb1QmXVYYrE0jv6DKEJ4Glc2SssT/4jAkx1LywVT1RI+bNFneHLNonbEWbPmz+hQl
         o+Wh7yCLeUpSTtn4jVyQ7WQ9Ggg8/1S4RtiHCobCiEMqL1DSTcIQMdJyptB59Gn1St3j
         2Skg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=1e100.net; s=20130820;
        h=x-gm-message-state:mime-version:in-reply-to:references:date
         :message-id:subject:from:to;
        bh=1gst8wLNhuRkPheZ8KuCI3b7Sj15ntjEdpHpSCsQIwU=;
        b=MSYiIj3Jd6DrFkDnEjMO/BeYyl7mW2zeoQiiZ21LkGmz6BR6eVllM0K0AgAzlp4zx3
         2IpLHEddD4vgpzNLfkwA3vV1t+TO+IcNoOebQxfxTPOWSnBsoixTKxi2454rqX1GO2Al
         PYP/WCeej83kpjnfMDK8FhOXimgtJeF7vg5spPdoekiL355e/Zz4AK1Fw7aMsp+xw76J
         CqaNUOza7DC5gwJQREinG/J3PAD0dzYCNEfdWQf8YkDzTl8Pq98EtR+TuUwtTn6x9Jjl
         +AfB1A+dsRalqZDoiUQkA2OxX3lheGi6JB9+qoXOfgt3+zQRLxC9l2xa1OFM+lWwqcth
         0Y4g==
X-Gm-Message-State: AD7BkJKY0973yuwy82MCxh7DvkNy8gobVal7HFwdX5EdusdNcFL6XtV1foPNe/cKREFUlWipkdi6//S9S+gmpQ==
MIME-Version: 1.0
X-Received: by 10.28.125.211 with SMTP id y202mr488856wmc.18.1456430946436;
 Thu, 25 Feb 2016 12:09:06 -0800 (PST)
In-Reply-To: <201602251908.u1PJ8K37010188@envy.delorie.com>
References: <CAC4O8c_VGVSJ293PtQOj-YNan0TYnYadJHAQ8iAXN8ccg4pK9A AT mail DOT gmail DOT com>
	<201602250321 DOT u1P3Lbr3003187 AT envy DOT delorie DOT com>
	<CAC4O8c-nHp9sD50sKyP7DbcuCytZ_Lop4aCBqpRAPnaNXK=EvA AT mail DOT gmail DOT com>
	<201602250338 DOT u1P3cpuB003688 AT envy DOT delorie DOT com>
	<CAC4O8c_gKOdh26-wHsBLnGrC+akBuin8AeqaL4H+OAOh8LkiLA AT mail DOT gmail DOT com>
	<201602250358 DOT u1P3wv4i004224 AT envy DOT delorie DOT com>
	<CAC4O8c928Q-Vs4RwVKhN51ANzFxdeZV0w-Afna+UkoT8Cea5Rw AT mail DOT gmail DOT com>
	<201602251705 DOT u1PH5ZXW003698 AT envy DOT delorie DOT com>
	<CAC4O8c_2zru30MPf-=-NSV5CGKnevfoYi1=Uo-bY_wXYm98h9Q AT mail DOT gmail DOT com>
	<201602251858 DOT u1PIwcsi009763 AT envy DOT delorie DOT com>
	<CAC4O8c8_-RP_V+JVNSXvv+Vnsk0XPA+1Ab-4emtXVGS2=iP+DA AT mail DOT gmail DOT com>
	<201602251908 DOT u1PJ8K37010188 AT envy DOT delorie DOT com>
Date: Thu, 25 Feb 2016 11:09:06 -0900
Message-ID: <CAC4O8c-uDg2PdgyJo0CcYRaWO+azXz3+mj9Ubu0Fgc7Cm1ng_Q@mail.gmail.com>
Subject: Re: [geda-user] exactly how is moving between sides/layers supposed
 to work, and more generally...
From: "Britton Kerin (britton DOT kerin AT gmail DOT com) [via geda-user AT delorie DOT com]" <geda-user AT delorie DOT com>
To: geda-user AT delorie DOT com
Content-Type: text/plain; charset=UTF-8
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 Thu, Feb 25, 2016 at 10:08 AM, DJ Delorie <dj AT delorie DOT com> wrote:
>
> I'm saying that it's a different way of doing things, not a "faster"
> or "better" way.  But different people want different things, so
> please don't make some of them suffer just because you don't agree
> with them.

Can you please just believe me when I say I have NO DESIRE to do that?
 It's why I'm asking here.  I'm grateful for Stephan's explanation of
the current pattern.

And you're obviously and rightly not going to let me do anything
destructive anyway.

The thing is, based on my own experience with pcb interface and
reasoning about it, I'm pretty sure there's room for improvement and
would like to sort out how.  Just adding a bunch of tooltips
documenting strange behavior is less than perfectly satisfying.  John
has a point when he says extra menu items and such are costly.  If two
are almost identical one could perhaps be deprecated or something.
The behavior of the import at mark thing is odd enough I strongly
suspect very few people are successfully using it, and since there's
an adjacent feature that does the same thing it could in theory point
to the neighboring feature for a while then someday go away.

Britton