Author Topic: Clickable URLs  (Read 7743 times)

phred

  • Global Moderator
  • Sr. Member
  • *****
  • Posts: 9348
Currently I put notes and other information in the comments field of many tracks. This will often include a URL to where the information came from or some other information related to the track.

The URL is displayed when viewing the comments but it is useless. I have to open the Tag Editor and copy the URL from the comments, close the Tag Editor, open a browser, and paste in the URL.

Making the URL clickable directly from the displayed comments would be great. OR make it possible to select/highlight the URL in the displayed comments so it can at least be copied directly from the comments without having to open the Tag Editor.

Thanks for considering.
Download the latest MusicBee v3.5 or 3.6 patch from here.
Unzip into your MusicBee directory and overwrite existing files.

----------
The FAQ
The Wiki
Posting screenshots is here
Searching the forum with Google is  here

The Incredible Boom Boom

  • Sr. Member
  • ****
  • Posts: 1269
Notwithstanding @hiccup's excellent workaround, this could actually be a new function for v3.5?

Code
The most awesomest music manager ever made is $URL(<Tag>,"https://getmusicbee.com","MusicBee") and best of all it's free!
The most awesomest music manager ever made is MusicBee and best of all it's free!

phred

  • Global Moderator
  • Sr. Member
  • *****
  • Posts: 9348
Auto Hotkey portion of thread split to Beyond MusicBee
https://getmusicbee.com/forum/index.php?topic=36013.0
Last Edit: January 08, 2022, 05:19:33 PM by phred
Download the latest MusicBee v3.5 or 3.6 patch from here.
Unzip into your MusicBee directory and overwrite existing files.

----------
The FAQ
The Wiki
Posting screenshots is here
Searching the forum with Google is  here

phred

  • Global Moderator
  • Sr. Member
  • *****
  • Posts: 9348
Specifically I'm referring to the URL as displayed in Track Information (1 or 2) as shown. In this case, Details (2) is set to only display comments.
Download the latest MusicBee v3.5 or 3.6 patch from here.
Unzip into your MusicBee directory and overwrite existing files.

----------
The FAQ
The Wiki
Posting screenshots is here
Searching the forum with Google is  here

hiccup

  • Sr. Member
  • ****
  • Posts: 7860
Me repenting for derailing this wish earlier:

+2

phred

  • Global Moderator
  • Sr. Member
  • *****
  • Posts: 9348
Notwithstanding @hiccup's excellent workaround, this could actually be a new function for v3.5?
What's wrong for including it in a patch release for 3.4?
Download the latest MusicBee v3.5 or 3.6 patch from here.
Unzip into your MusicBee directory and overwrite existing files.

----------
The FAQ
The Wiki
Posting screenshots is here
Searching the forum with Google is  here

The Incredible Boom Boom

  • Sr. Member
  • ****
  • Posts: 1269
What's wrong for including it in a patch release for 3.4?

Nothing.
Just assuming @Steven might be winding down cool new features for v3.4 at this point and focusing on issues.
I have nothing to base this off of, however.

phred

  • Global Moderator
  • Sr. Member
  • *****
  • Posts: 9348
Ahhh .. thanks for clarifying, BB.
Download the latest MusicBee v3.5 or 3.6 patch from here.
Unzip into your MusicBee directory and overwrite existing files.

----------
The FAQ
The Wiki
Posting screenshots is here
Searching the forum with Google is  here


Steven

  • Administrator
  • Sr. Member
  • *****
  • Posts: 34346
I will look at this request.If some text starts with http:// or https:// then it could be made clickable but for multi-line text such as comments that wraps around, it would only be feasible for me to do this if a line starts with the http text ie. this wouldnt be supported
Code
xxx http://aaa.com xxx
but this would:
Code
xxx
http://aaa.com
xxx

phred

  • Global Moderator
  • Sr. Member
  • *****
  • Posts: 9348
I will look at this request.
Thanks Steven.

I don't think what you're proposing would be an issue for my use case. As long as it will work with both http: and https:
Doing a random check on the links in my comments, I couldn't find one instance where there was a <space> and variable after the actual URL.

This is typical:
Download the latest MusicBee v3.5 or 3.6 patch from here.
Unzip into your MusicBee directory and overwrite existing files.

----------
The FAQ
The Wiki
Posting screenshots is here
Searching the forum with Google is  here

mrbenn

  • Full Member
  • ***
  • Posts: 168
FWIW, Bandcamp downloads consistently have a comment in the URL in the format

Code
Visit http://artistorlabel.bandcamp.com

Some artists/labels use their own custom domain but the comment format itself is the same.

Steven

  • Administrator
  • Sr. Member
  • *****
  • Posts: 34346
Unfortunately there are some complications so I wont be able to do the request as stated. However what I have done is add a new data type: Url
So if you assign a custom tag or virtual tag the data type: Url (in the Tags(2)/ Fields Configuration dialog) then the field will be treated as a clickable link in the track info panel. Of course that wont work if the link is embedded in the middle of a comment (for example) as the entire field value is treated as the link

phred

  • Global Moderator
  • Sr. Member
  • *****
  • Posts: 9348
Of course that wont work if the link is embedded in the middle of a comment (for example) as the entire field value is treated as the link
My first thought is that Advanced Search & Replace might be able to make the move. If it doesn't I can do a simple search for "http" in comments and manually move them. At this point I'd guess I have less than 100, but there are more that I'd like to add and have been holding off.

Bottom line is that this should do what I've been asking for.

Thank you.
Download the latest MusicBee v3.5 or 3.6 patch from here.
Unzip into your MusicBee directory and overwrite existing files.

----------
The FAQ
The Wiki
Posting screenshots is here
Searching the forum with Google is  here

hiccup

  • Sr. Member
  • ****
  • Posts: 7860
My first thought is that Advanced Search & Replace might be able to make the move. If it doesn't I can do a simple search for "http" in comments and manually move them.
Wouldn't a virtual tag be easier?
Could you for example give this one a test drive?:

Code
$RxMatch(<Comment>,"(^|\s)https?\:\S*|(^|\s)www\.\S*")