kicad-developers team mailing list archive
-
kicad-developers team
-
Mailing list archive
-
Message #28687
Re: Footprint filter match behavior
-
To:
kicad-developers@xxxxxxxxxxxxxxxxxxx
-
From:
Clemens Koller <cko@xxxxxxxxx>
-
Date:
Tue, 14 Mar 2017 17:47:18 +0100
-
In-reply-to:
<20170314155713.GA14948@turnip.local>
-
User-agent:
Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
Yes, please!
*R* -> R somewhere in the name.
R* -> R in the beginning of the name.
*R -> R at the end of the name.
R*1005M*1* are 1005M (0402) sized resistors with different values starting with 1
1, 10, 100, 1.2, 12, 120, 15. ... [k|M]Ohms as i.e.:
R-1005M-1R0 (1Ohm)
R-1005M-103 (10kOhm)
R-1005M-184 (180kOhm)
Optionally an SQL LIKE "%" Symbol could be nice to be used optionally as a wildcard.
See: https://www.w3schools.com/sql/sql_wildcards.asp
Because... in the long term, we propably want to put everything into a database anyway. ;-)
Regards,
Clemens
On 2017-03-14 16:57, Chris Pavlina wrote:
> Hi,
>
> Currently, the footprint filter strings in a component match a footprint
> if they occur *anywhere* in the footprint's name. This leads to some
> possibly unintentional matches - for example, "R" has a filter "R_*",
> which matches literally every footprint with R_ somewhere in its name.
> This is quite a lot of footprints that are NOT resistors.
>
> What if I changed this to require matching at the beginning of the
> string? A filter meant to match anywhere in the string could be written
> "*R_*" instead. This should significantly reduce the number of false
> positive matches.
>
References