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
         :content-type;
        bh=B0NA2mDhy/fxEjd/GZBt9y9PJf9BCvFy0Ln1Z9ik8NE=;
        b=dbAC75OvOYN+tb8YhcOFKnlO5s1nvtdnXX3PmeFGVKmOw1v+T5QERvFSaHxfmFx+zT
         tVerju6+oBbNKJuLRME0m/5OuuUsF+fkZmjVA1jIx4FKcLLEiLsTHYvzf62SmQhvaUAf
         Pzgw4qv3qOZNITSiu1g3iVG/HjELmj8aZJrIsyjQYrpVbeKV5wqv/YcAMQbuLUmLV6Mz
         a2oYdKhQ42WjdvF8buMYBhg7r4Ua0Um8wRLmb0dvn/4DjnEju2mplY92Vq//mOjU7ZdK
         ZhV9nxHVHXjlFW23t9jQX/6z5T44iAZhb1+6KLsYSbHVcyCAbtaD38HcFqu1kbf89A4r
         CB3Q==
MIME-Version: 1.0
X-Received: by 10.107.136.152 with SMTP id s24mr10318766ioi.165.1438789201026;
 Wed, 05 Aug 2015 08:40:01 -0700 (PDT)
In-Reply-To: <55C21FC5.2030100@ecosensory.com>
References: <818820A7-34E1-4EE3-B043-992FA380ED01 AT sbcglobal DOT net>
	<mpor01$v3h$1 AT ger DOT gmane DOT org>
	<3043CCB2-68EE-4CC4-BDAD-C5DBB035070B AT sbcglobal DOT net>
	<3CA1F410-AE98-4F43-8DFC-C3671A4A4B90 AT noqsi DOT com>
	<39FCD9DF-3848-4819-BFE3-1E9C6D5D2970 AT sbcglobal DOT net>
	<mprp09$7ih$1 AT ger DOT gmane DOT org>
	<201508050138 DOT t751c3N3026160 AT envy DOT delorie DOT com>
	<CAC4O8c9RYgjC9WQcfLmrUx2=aaMBMmWR7PbWOPm4npUC-ncdLw AT mail DOT gmail DOT com>
	<55C21FC5 DOT 2030100 AT ecosensory DOT com>
Date: Wed, 5 Aug 2015 08:40:00 -0700
Message-ID: <CAOP4iL3XFJRuC899hBp5QYrVwcQ=L=8ZX-yGoBHqH+LZJ6XQuw@mail.gmail.com>
Subject: Re: [geda-user] Find Text Mechanism
From: "Ouabache Designworks (z3qmtr45 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: multipart/alternative; boundary=001a113ed2143be224051c9237f4
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

--001a113ed2143be224051c9237f4
Content-Type: text/plain; charset=UTF-8

On Wed, Aug 5, 2015 at 7:37 AM, John Griessen <john AT ecosensory DOT com> wrote:

> On 08/04/2015 09:46 PM, Britton Kerin (britton DOT kerin AT gmail DOT com) [via
> geda-user AT delorie DOT com] wrote:
>
>> I really dislike such setups, you can't work
>> same on laptop and its sort of a substitute for UI failures and slowness
>> to
>> need all that extra space.
>>
>
>
> It's not an either or thing.  We can have both, and that's mostly true for
> any
> new feature since we are such a cat herd, or non-herd of individuals.
> New features need to be configurable to leave off, or connect to
> key-bindings
> or various menus.  Upgrades should not force change on users that have
> config files set.   Probably even to the point that if there is a new
> feature
> and the config file does not set it up, leave it inactive.  Only notify
> users
> of existence rather than enabling new features.
>
> Sounds odd, bu that would match current set of users.
>


One of the problems in the current code is that the menus are defined in
the system-gschemrc file but there is no command that will reset the menus
back to their zero state. If there was then if you didn't like the out of
box defaults then you could copy the gschemrc file locally and do it your
way.

The reset menus command is in the code but it seems to need a linkage
command that calls the low level command from the gschemrc file.

John Eaton

--001a113ed2143be224051c9237f4
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><br><div class=3D"gmail_extra"><br><div class=3D"gmail_quo=
te">On Wed, Aug 5, 2015 at 7:37 AM, John Griessen <span dir=3D"ltr">&lt;<a =
href=3D"mailto:john AT ecosensory DOT com" target=3D"_blank">john AT ecosensory DOT com</=
a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0=
 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class=3D"">On =
08/04/2015 09:46 PM, Britton Kerin (<a href=3D"mailto:britton DOT kerin AT gmail DOT c=
om" target=3D"_blank">britton DOT kerin AT gmail DOT com</a>) [via <a href=3D"mailto:g=
eda-user AT delorie DOT com" target=3D"_blank">geda-user AT delorie DOT com</a>] wrote:<b=
r>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
I really dislike such setups, you can&#39;t work<br>
same on laptop and its sort of a substitute for UI failures and slowness to=
<br>
need all that extra space.<br>
</blockquote>
<br>
<br></span>
It&#39;s not an either or thing.=C2=A0 We can have both, and that&#39;s mos=
tly true for any<br>
new feature since we are such a cat herd, or non-herd of individuals.<br>
New features need to be configurable to leave off, or connect to key-bindin=
gs<br>
or various menus.=C2=A0 Upgrades should not force change on users that have=
<br>
config files set.=C2=A0 =C2=A0Probably even to the point that if there is a=
 new feature<br>
and the config file does not set it up, leave it inactive.=C2=A0 Only notif=
y users<br>
of existence rather than enabling new features.<br>
<br>
Sounds odd, bu that would match current set of users.<br>
</blockquote></div><br><br></div><div class=3D"gmail_extra">One of the prob=
lems in the current code is that the menus are defined in the system-gschem=
rc file but there is no command that will reset the menus back to their zer=
o state. If there was then if you didn&#39;t like the out of box defaults t=
hen you could copy the gschemrc file locally and do it your way.<br><br></d=
iv><div class=3D"gmail_extra">The reset menus command is in the code but it=
 seems to need a linkage command that calls the low level command from the =
gschemrc file.<br><br></div><div class=3D"gmail_extra">John Eaton<br><br><b=
r></div></div>

--001a113ed2143be224051c9237f4--