X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f
Date: Mon, 5 Oct 2015 13:22:16 -0400
Message-Id: <201510051722.t95HMGaj025044@envy.delorie.com>
From: DJ Delorie <dj AT delorie DOT com>
To: geda-user AT delorie DOT com
In-reply-to: <20151005180922.f9720de6c048092686e81761@gmail.com>
	(geda-user AT delorie DOT com)
Subject: Re: [geda-user] Clutterless user interface or even more custom
 special super features?
References: <56100AF8 DOT 4090802 AT jump-ing DOT de>
	<muq108$s12$1 AT ger DOT gmane DOT org>
	<20151005072529 DOT GA26068 AT visitor2 DOT iram DOT es>
	<CAJZxidAqEJv+0eSMbnOH39y-ThoXDZitv1w56Gmj0Q4y0paNAA AT mail DOT gmail DOT com>
	<20151005153014 DOT 1af231ef2d4eee97a0dd0054 AT gmail DOT com>
	<201510051505 DOT t95F5uRI019817 AT envy DOT delorie DOT com> <20151005180922 DOT f9720de6c048092686e81761 AT gmail DOT com>
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


> It is also possible to add a list with objects listed by selectors
> like for example: layer, Refdes, footprint value, object type, ...

I can see that being useful, but I also see it being complex and
difficult to implement in an intuitive way.  For example, if you only
check certain layers, but also check "lines", do those choices
intersect, or union?  What about merging "vias" with a refdes filter?
(yes, vias can be named, just like elements).  If you only enable
lines, should we disable the via tool?  And if one of the selection
filter options is "locked items" how does that change how we merge
options?

Internally, we'd need some standard rules as well, for cases where the
tool being used needs to filter out things it can't operate on, and
how to combine those rules with user-selected rules.