Author Topic: Add "Love" field type to allow replicating Love column functionality  (Read 96 times)

eugenesv

  • Jr. Member
  • **
  • Posts: 30
This is based on https://getmusicbee.com/forum/index.php?topic=43111.msg236634#msg236634

The idea is to be able to replicate the love /ban UI functionality with a custom user tag in the same way you can do it for the rating tag.
While currently you can partially replicate the looks and data in a custom Love tag, but you can't replicate the ease of a single click to set the love/ban value

The original reason was to be able to have custom rating/love tags for different users in the same database.

boroda

  • Hero Member
  • *****
  • Posts: 5249
+100, but not "love" type. it will be better if we have custom clickable 2-state fields, which have 2 chars/strings for displaying purposes and 2 another strings for saving 1 of them to custom tag on mouse click. i see much more use cases for these fields than just additional "love" status.

tjinc

  • Sr. Member
  • ****
  • Posts: 836
I don't think you could introduce multiple Love/Ban fields due to the functionality of the 'ban' setting:

When a track is 'banned' it is prevented from being selected for auto-playlists and is prevented from being played in many situations. If you had two Love/Ban fields, a single track could be both 'loved' and 'banned'.
(It would be unfair to ask MusicBee to decide and hence take sides in a domestic dispute of whether a track should be played or not.  :) )

A clickable Boolean type field sounds a little more interesting, especially if you could define the yes/no characters or strings to be displayed.
(Having said that, I will note that the <Ticked> field is already available, albeit somewhat visually unappealing, and I have never used this.)

eugenesv

  • Jr. Member
  • **
  • Posts: 30
That's fine if the widespread ban functionality is tied to the primary love, you could still add filters to playlists etc to exclude bans if you like.
What is missing now is the convenience of setting the value

Would the binary field you suggest allow maintaining the original data of the love field (helpful since that field is recognized in some other apps)? If is strictly a more general solution that seems better.