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=date:from:to:subject:message-id:in-reply-to:references:mime-version :content-type:content-transfer-encoding; bh=wQduBIeLaXUg2V4m8scKUALkqF3oNUW0A05NenlBRfo=; b=GeL9rBG/iQm4COvPJs2yezQ878dYvH0/325KB3mgjiGnHGMJCLhyMuqFEQrmJud/Fd PqUZp5NmV3i7thIjkDHPcaB367DiWe8bt4NVvFg4SzicHccfrrG1e6LiPjExOJ0FmD+m ozc+519Q0HYV/FvXbD/7ccwEMHpBtV/JuA3wqBYc9gkxyrbTmePGvIxqr4D6IFGgIhX4 Q2yMMCiS+yf014ZnYYCNIahLeLsrbixht2KcfPvLwt2PiCOhwL4xs3BjPFSwTKEAfjFl 6K6UJSltGrpc7tePoUuDyGXY8IuGBWR1cGljcj8G2s+ha39sC3nmok9sXzTEAAgEyJNj 1Y8Q== X-Received: by 10.195.11.165 with SMTP id ej5mr22602994wjd.117.1444068911933; Mon, 05 Oct 2015 11:15:11 -0700 (PDT) Date: Mon, 5 Oct 2015 20:15:06 +0200 From: "Nicklas Karlsson (nicklas DOT karlsson17 AT gmail DOT com) [via geda-user AT delorie DOT com]" To: geda-user AT delorie DOT com Subject: Re: [geda-user] Clutterless user interface or even more custom special super features? Message-Id: <20151005201506.e85ead5b3b2e0e83821b1fa9@gmail.com> In-Reply-To: <201510051722.t95HMGaj025044@envy.delorie.com> References: <56100AF8 DOT 4090802 AT jump-ing DOT de> <20151005072529 DOT GA26068 AT visitor2 DOT iram DOT es> <20151005153014 DOT 1af231ef2d4eee97a0dd0054 AT gmail DOT com> <201510051505 DOT t95F5uRI019817 AT envy DOT delorie DOT com> <20151005180922 DOT f9720de6c048092686e81761 AT gmail DOT com> <201510051722 DOT t95HMGaj025044 AT envy DOT delorie DOT com> X-Mailer: Sylpheed 3.5.0beta1 (GTK+ 2.24.25; x86_64-pc-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit 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. Another option is to use a tree view like in PADS instead of a search filter. I think result would be the same for example to show all footprints of the same type on a particular layer it is possible with a tree view or two selectors layer=value,footprint=value. I should look at zorn some day maybe I could give it a try in gEDA.