# Wish filter expressions \<field\> HAS \<field\>

**URL:** https://community.mp3tag.de/t/wish-filter-expressions-field-has-field/10011
**Category:** General Discussion
**Created:** [March 2, 2010, 9:53am UTC](https://community.mp3tag.de/t/wish-filter-expressions-field-has-field/10011 "2010-03-02T09:53:10Z")
**Posts on this page:** 14
**Page:** 1

<div class="post-metadata">

### Author: ![incifinci](https://community.mp3tag.de/user_avatar/community.mp3tag.de/incifinci/32/6526_2.png) [@incifinci](https://community.mp3tag.de/u/incifinci)
#### Post date: [March 2, 2010, 9:53am UTC](https://community.mp3tag.de/t/wish-filter-expressions-field-has-field/10011/1 "2010-03-02T09:53:10Z")

</div>

It will be very nice - of course with ability to use functions too.  
For example: **NOT "$left(%\_parent\_directory%,3)" IS "$left(%artist%,3)"**

And will be nice too to save "forever" some important filters. Now I can't use the new feature Shift+Delete history, because I have 40-50 complex filter expressions what I don't want to delete. Method may be with horizontal line in filter history (the expressions under line will not deleted with Shift) or a button with dropdown list on toolbar or any else.

More: will be useful the ability to reorder filter expressions in history - and in all history lists too.

---

<div class="post-metadata">

### Author: ![dano](https://community.mp3tag.de/user_avatar/community.mp3tag.de/dano/32/6_2.png) [@dano](https://community.mp3tag.de/u/dano)
#### Post date: [March 2, 2010, 8:36pm UTC](https://community.mp3tag.de/t/wish-filter-expressions-field-has-field/10011/2 "2010-03-02T20:36:17Z")

</div>

You can use  
"$if($eql($left(%\_parent\_directory%,3),$left(%artist%,3)),1,0)" IS 0

---

<div class="post-metadata">

### Author: ![incifinci](https://community.mp3tag.de/user_avatar/community.mp3tag.de/incifinci/32/6526_2.png) [@incifinci](https://community.mp3tag.de/u/incifinci)
#### Post date: [March 3, 2010, 8:52am UTC](https://community.mp3tag.de/t/wish-filter-expressions-field-has-field/10011/3 "2010-03-03T08:52:25Z")

</div>

Really, it works. Thank you!

---

<div class="post-metadata">

### Author: ![incifinci](https://community.mp3tag.de/user_avatar/community.mp3tag.de/incifinci/32/6526_2.png) [@incifinci](https://community.mp3tag.de/u/incifinci)
#### Post date: [March 10, 2010, 5:12am UTC](https://community.mp3tag.de/t/wish-filter-expressions-field-has-field/10011/4 "2010-03-10T05:12:32Z")

</div>

> [@incifinci](#):
>
> And will be nice too to save "forever" some important filters. Now I can't use the new feature Shift+Delete history, because I have 40-50 complex filter expressions what I don't want to delete. Method may be with horizontal line in filter history (the expressions under line will not deleted with Shift) or a button with dropdown list on toolbar or any else.
> 
> More: will be useful the ability to reorder filter expressions in history - and in all history lists too.

**Idea** : the simplest way to make these changes in use of **history lists** : not to include them into .cfg file, but to separate them **in individual files** like, for example, .mte files.

---

<div class="post-metadata">

### Author: ![Florian](https://community.mp3tag.de/user_avatar/community.mp3tag.de/florian/32/5759_2.png) [@Florian](https://community.mp3tag.de/u/Florian)
#### Post date: [April 13, 2022, 9:18am UTC](https://community.mp3tag.de/t/wish-filter-expressions-field-has-field/10011/5 "2022-04-13T09:18:54Z")

</div>

I've added an option to manage the filter list, including named filters and reordering with [Mp3tag v3.14b](https://community.mp3tag.de/t/455).

---

<div class="post-metadata">

### Author: ![incifinci](https://community.mp3tag.de/user_avatar/community.mp3tag.de/incifinci/32/6526_2.png) [@incifinci](https://community.mp3tag.de/u/incifinci)
#### Post date: [April 13, 2022, 9:54am UTC](https://community.mp3tag.de/t/wish-filter-expressions-field-has-field/10011/6 "2022-04-13T09:54:02Z")

</div>

Thank you, perfect solution. Unfortunately, with a little carelessness: something has changed with the language encoding. For example, earlier written törpe now seems tĂ¶rpe. If i type it again by hand, it stays correct. (But i am waiting to see, if you want to change anything, may be.)

---

<div class="post-metadata">

### Author: ![Florian](https://community.mp3tag.de/user_avatar/community.mp3tag.de/florian/32/5759_2.png) [@Florian](https://community.mp3tag.de/u/Florian)
#### Post date: [April 13, 2022, 10:01am UTC](https://community.mp3tag.de/t/wish-filter-expressions-field-has-field/10011/7 "2022-04-13T10:01:58Z")

</div>

Thanks for pointing. It's a UTF-8 conversion issue which I'll fix very soon...

---

<div class="post-metadata">

### Author: ![incifinci](https://community.mp3tag.de/user_avatar/community.mp3tag.de/incifinci/32/6526_2.png) [@incifinci](https://community.mp3tag.de/u/incifinci)
#### Post date: [April 13, 2022, 10:03am UTC](https://community.mp3tag.de/t/wish-filter-expressions-field-has-field/10011/8 "2022-04-13T10:03:28Z")

</div>

Other. After the first use (OK and closed), if i click on the small arrow (to handle the filters again), the list will be almost full windowed. (It certainly affects: i have a lot of filters, and some are pretty long.) It was not like that before. Whether it is planned or not, i do not know. Whether it is practical or not, I do not (yet) know (though more likely it is practical).

It is also important: this is the case only, if i have left the long lines checked (in the manager). That is, it depends on the length of the **marked** filters. By the way, this marking option is a great new feature, thank you!

---

<div class="post-metadata">

### Author: ![Florian](https://community.mp3tag.de/user_avatar/community.mp3tag.de/florian/32/5759_2.png) [@Florian](https://community.mp3tag.de/u/Florian)
#### Post date: [April 13, 2022, 10:20am UTC](https://community.mp3tag.de/t/wish-filter-expressions-field-has-field/10011/9 "2022-04-13T10:20:46Z")

</div>

> [@incifinci](#):
>
> something has changed with the language encoding. For example, earlier written törpe now seems tĂ¶rpe.

It's fixed with [Mp3tag v3.14c](https://community.mp3tag.de/t/455). It will take your pre-v3.14b filter expressions and convert them correctly, so no data should be lost (except for what you've added and edited in the past minutes with v3.14b).

---

<div class="post-metadata">

### Author: ![Florian](https://community.mp3tag.de/user_avatar/community.mp3tag.de/florian/32/5759_2.png) [@Florian](https://community.mp3tag.de/u/Florian)
#### Post date: [April 13, 2022, 10:23am UTC](https://community.mp3tag.de/t/wish-filter-expressions-field-has-field/10011/10 "2022-04-13T10:23:04Z")

</div>

> [@incifinci](#):
>
> It is also important: this is the case only, if i have left the long lines checked (in the manager). That is, it depends on the length of the **marked** filters.

Yes, but you can also specify a **Name** for these extra long items which will then be used in the menu instead of the long format string. I'll think about trimming those extra long strings to a reasonable size in the menu — thanks for pointing.

---

<div class="post-metadata">

### Author: ![incifinci](https://community.mp3tag.de/user_avatar/community.mp3tag.de/incifinci/32/6526_2.png) [@incifinci](https://community.mp3tag.de/u/incifinci)
#### Post date: [April 13, 2022, 10:23am UTC](https://community.mp3tag.de/t/wish-filter-expressions-field-has-field/10011/11 "2022-04-13T10:23:49Z")

</div>

Yes, the encoding is perfect; thank you, Florian.

(Fixed in 20 minutes... I have never seen such support.)

---

<div class="post-metadata">

### Author: ![incifinci](https://community.mp3tag.de/user_avatar/community.mp3tag.de/incifinci/32/6526_2.png) [@incifinci](https://community.mp3tag.de/u/incifinci)
#### Post date: [April 13, 2022, 10:27am UTC](https://community.mp3tag.de/t/wish-filter-expressions-field-has-field/10011/12 "2022-04-13T10:27:26Z")

</div>

> [@Florian](#):
>
> I'll think about trimming those extra long strings to a reasonable size in the menu

I agree, seems to be the best compromise.

> [@Florian](#):
>
> but you can also specify a **Name** for these extra long items

Really! Thank you for pointing.

---

<div class="post-metadata">

### Author: ![incifinci](https://community.mp3tag.de/user_avatar/community.mp3tag.de/incifinci/32/6526_2.png) [@incifinci](https://community.mp3tag.de/u/incifinci)
#### Post date: [April 13, 2022, 11:12am UTC](https://community.mp3tag.de/t/wish-filter-expressions-field-has-field/10011/13 "2022-04-13T11:12:43Z")

</div>

Also useful: it is now possible to delete the filter quickly. You need to add a new filter. Its content is nothing, its name is **Empty the filter** (or any similar). It should be pulled on top. It can be used quickly with the mouse (selecting the "filter" in the old, usual way).

---

<div class="post-metadata">

### Author: ![system](https://community.mp3tag.de/uploads/default/original/2X/c/ce7035d426cb755a7916793326d23b465222a407.png) [@system](https://community.mp3tag.de/u/system)
#### Post date: [May 13, 2022, 11:13am UTC](https://community.mp3tag.de/t/wish-filter-expressions-field-has-field/10011/14 "2022-05-13T11:13:06Z")

</div>

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.
