Custom LOVE rating column behaving like the default

[eugenesv]

Is there a way to create an identical (in behavior) tag/column for a custom LOVE rating? I've created a custom-named tag, copied the LOVE rating field value to it (which is represented as L for love and B for ban), set the same tag type (string) for the new rating as it's set for the default one, but I only get the L/B text in that field, not the icons. And while I can add another custom column that would read l/b values and set icons manually (though they'd look slighly different), I wouldn't be able to change the status by clicking on the column

(interestingly enough, even if I create a cusom column with a value of the <Loved> tag, I only get "Loved"/"Banned" (not "L"/"B" like seen in mp3tag))

So it seems that the click-to-set is custom-coded for just that unique column and not a general property of the "loved" field?

[tjinc]

So it seems that the click-to-set is custom-coded for just that unique column and not a general property of the "loved" field?

Correct, this is a hard-coded function for this field only - I don't believe that you can create a custom field with the same functionality.

[hiccup]

What would come very close is:

-  set the field to 'Enumerated'
-  make sure that at least one song has that tag populated with the unicode ❤️ character.
​
After that you would have something like this:

[eugenesv]

Thanks, but that would break the L/B values that I use to match the default tag since I synced those fields with the original Loved tag.

[hiccup]

I'm not sure I fully understand what you are trying to accomplish, or what your actual workflow is.

Now I am thinking that you want your 'CustomLove' column to represent what is in the actual 'Love' tag, but you also want to be able to modify the value in 'CustomLove', and that such a change will also affect 'Love'?

I probably misunderstand because that would not make much sense.

[eugenesv]

No, I want my 'CustomLove' column to be compatible with the actual 'Love' one so I could easily move values from one to another and also use the same formulas in my virtual tags without having to worry about different values (L vs unicode ❤️). The changes will be separate.

The overarching idea is to be able to have love tags for multiple people in the same library that behave identically UI-wise

[hiccup]

That will be somewhat complicated indeed, but I think modifying your existing virtual tags using something along the lines of this may work:

$If($Or(<Love>="L",<CustomLove>="❤️"),love,)

Maybe I'm still not getting it, but I am going to leave it at this anyway ;-)

[boroda]

$If($Or(<Love>="L",<CustomLove>="❤️"),love,) won't work because empty parameters are not supported, but this may work:

$If($Or(<Love>="L",<CustomLove>="❤️"),"love","")

[hiccup]

"won't work because empty parameters are not supported…"

It will work, since MusicBee will add the quotes automatically ;-)

(maybe that isn't the case with AT&RT though?)

[boroda]

you are right 

[eugenesv]

$If($Or(<Love>="L",<CustomLove>="❤️"),love,)

Thanks for trying to help! But this only affects the visual part, doesn't help with the convenience of editing (by the way, is it possible like in mp3tag to have a column display some complicated text from multiple tags like in this formula, but edit only a specific tag like <CustomLove>?), and still leaves the data incompatible, so you wouldn't be able to simply copy from one loved tag to another, but would need to create more rules to convert Ls into ❤️s and vice versa and remember to use them instead of the more common copy tags operation.

[karbock]

Whereas there is only one "Love" tag,
you can have several custom tags that behave like the standard "Rating" tag.

To assign that behaviour:
Preferences -> tab "Tags (2)" -> button [Configure Fields...] -> select "Rating" as Type.
(It's only possible for custom tags.)

[eugenesv]

Thanks, I know and use the custom rating for the same purpose, that's exactly what prompted this question - was wondering how to do the same for a love rating

[karbock]

You could add the topic to the Wishlist:
adding "Love" to the field types in the Fields Layout Editor.

You'll see if your proposal gets support, and/or is easily feasible.
User proposes, Steven disposes. As the (just coined) saying goes.

[eugenesv]

Good idea, added to the suggestions

https://getmusicbee.com/forum/index.php?topic=43118.0