Adding colour information messes with indentation

[SonicRings]

Short and sweet bug report.

$If(<Comment>="Unknown Comment",,<Comment>)$If(<Comment>="",," ///// ")Time Listened: <TimeListened>

The above produces this:



While the following:

$If(<Comment>="Unknown Comment",,<Comment>)$If(<Comment>="",," ///// "){color: 255,100,100} Time Listened: <TimeListened>

Produces this:



This is being done in a field here.

[The Incredible Boom Boom]

I also experience this. It noticed it occurring after one of the updates in this thread.

I've been experiencing this problem (I think it's the same) since this patch update and am just now getting around to sussing out how to fix it. Before this patch, I didn't have duplications with this particular Track Information code. Here's a representation. As displayed, both the track title and album name are duplicated.



...

If I remove the semi-colon and the checkmark splitting the field into multiple rows, I get this as the result.



Removing the markup tags doesn't make any difference in either case.

[Steven]

I dont see how the issue as reported by the OP would ever have worked as it would require special string measuring/ splitting to get the coloured text to wrap to the start of the next line.
I doubt i will be able to address this issue

[SonicRings]

I dont see how the issue as reported by the OP would ever have worked as it would require special string measuring/ splitting to get the coloured text to wrap to the start of the next line.
I doubt i will be able to address this issue

Ah, that's sad to hear. I guess for the track information panel, it's only possible to assign text attributes at the beginning, since putting it in the middle somehow makes wherever it was placed the location of the next newline.

I suppose a simple workaround would be to simply add more fields. It won't allow for different elements of a line to have different attributes, but in this particular instance I only did it this way because I had run out of fields and had to combine 2 different things into one, so at least it can allow for additional lines to be made normally.

[purplebee]

I was about to report this, thankfully I found this thread before creating a new thread. Given Steven's response I now understand why this would be complicated to fix. I might as well share my post before scrapping it though :

-----------

First of all, so this is easier to understand, this is how the track information works: There's a prompt field and a main field. Once a prompt field is set, it works as a sort of indentation for the main field. You can customize the number of rows each line takes and allow for longer tags to wrap around.

Issue #1: The number of rows doesn't always match with the field length. This was brought up a few years ago in this thread: https://getmusicbee.com/forum/index.php?topic=34118.0
Example:


At the time Steven mentioned it wouldn't be fixed due to the complexity of using multiple text formats, which is understandable. I tried to find a workaround by moving everything to the main field, which of course works well without formatting:


When formatting is added it also fixes some instances (but not all of them) of Issue #1:



This leads me to Issue #2, which is why I made this thread: When formatting is applied to the main field, the first piece of formatted text seems to be treated as a prompt, creating an indentation. I'm guessing this isn't the intended behavior of this field, as it's counterintuitive.

[hiccup]

…First of all, so this is easier to understand, this is how the track information works: There's a prompt field and a main field…

Apologies beforehand for me not having given everything that has been said and explained proper attention.
I only did some speed-reading on this lazy sunday evening.

Am I correct in thinking that this specifically concerns the 'prompt:' field?

I'm pretty sure there have been more than one reports on issues when applying text/font formatting options to that field.

So maybe somebody could try to figure out exactly what is going on with that, and then post either a Bug Report or a Wishilist request?
Speaking for myself, I have been avoiding to use (and/or apply formatting to) that field for exactly this reason.

[purplebee]

Am I correct in thinking that this specifically concerns the 'prompt:' field?[/i]

Not exactly, as shown in the original post even if you avoid using the prompt field, formatted text behaves similarly to the prompt field, adding indentation. As Steven's reply implies, it's a known limitation, and Musicbee isn't able to wrap around text with multiple formats.