Fixed Line Limit basic string

Feature requests
1

Feature description:

Add two fixed Line Limit basic string, their form is %ld% (line dead) & \o (line over)
outside {} use %ld%. it will identify the nearest %ld% in front of it, and the string betweent %lb% and %lb% will be limit in the line of the start line of this identified %lb%.If in front of %ld% have a {\n} (it must be take effect) in the font of the first nearset %lb%. %ld% will priority identify the nearest {\n}.And if in front of this %ld% do not indetify any effected {\n} or %lb%, it will function up to beginning of this string.
Inside {} use \o, inside {} and between \n and \o, these string inside {} if effected will be limited in one line.
And this Line Limit basic string also can associated the ellipsis rule of this String, “None / End ellipsis / Marquee” will direct function on the end of this Limit Line string .

Problem solved:

Sometime user might use the all 4 line of string one of the six. The relatively speaking shorter strings will be arranged in the first three line.The fourth line should arrange longer strings live with the %next.artist% %next.title%.But the first three line due not every song have same full tags.So in some case just show 1 2 4 line arranged strings.And by chance the next title is very long, that cause 3 4 Line booth be occupye,and the last line show the remaining part of next title, this looks very untidy.But the fixed Line Limit basic string can let it only stay in itself line, will solve this problem.

Brought benefits:

Make sure the specific line in one of six string can stay where it started.To avoid one too longer line string occupy remaining line to reduce the incongruity.And due this Limit basic string can associated the ellipsis rule of this String.It can match marquee mode to show itself line full information, not need to scroll with the entire 4 lines of characters.

Other application solutions:

 
It just for the situation of symfonium now playing custom string.To use this specific basic string made every line of one string have it order.Reduce the rich string user’s use restrictions.
 

Additional description and context:

 
The proposeed baisc string style for reference only, just to match the existed %lb% & \n.I think this feature can increase the diversity of custom string usage in now playing page of symfonium.
These is some example:
%lb%AAAAA%ld%
{\n𝐍𝐞𝐱𝐭-𝐀𝐥𝐛𝐮𝐦/𝐀𝐫𝐭𝐢𝐬𝐭 %next.album|player.remaining==“-00:14” %next.albumartist%\o}
And the Screenshot feature demo.
 

Screenshots / Mockup:

 

Screenshot 1
Screenshot 13000×2120 5.04 MB
   

2

I’m sorry but I have no idea what you are trying to explain

3

Feature Request: Line-Lock Tokens (%ld% & \o) for Now-Playing Strings

What it does

Introduce two “line-lock” tokens:

  • %ld% – used outside braces
  • \o – used inside braces

They pin the text that follows them to the same physical line where the nearest preceding %lb% or effective \n started.

If a \n exists immediately in front of that %lb%, the \n wins and the lock is anchored to its line.

If no anchor is found, the lock simply starts from the beginning of the string.

While the locked text is running, the ordinary ellipsis rules (“none / end-ellipsis / marquee”) are applied only to that single line, not to the whole 4-line block.

Problem it solves

Users often build 4-line now-playing cards from a 6-line pool.

Lines 1-3 usually hold short tags (album, artist, …).

Line 4 is reserved for “Next: %next.artist% – %next.title%”.

Because not every track has every tag, sometimes only lines 1, 2 and 4 render.

When the next title is very long, it spills over and occupies both the invisible line 3 and visible line 4, pushing the remainder of the title into the next physical row.

The result is an untidy staircase effect.

Locking line 4 to itself keeps the long “next” string inside its own row; overflow is handled by the chosen ellipsis mode (including marquee), so the rest of the layout stays clean.

Benefits

  • Guarantees that a given logical line always stays on the row where it started.
  • Prevents one unexpectedly long tag from stealing extra rows.
  • Lets the user enable marquee per line; the locked line scrolls independently instead of dragging the entire 4-line block.

Scope

The tokens are meant only for Symfonium’s now-playing custom strings.

They reuse the existing %lb% and \n syntax, so there is nothing new to learn.

Example

%lb%AAAAA%ld%{\nNext-Album/Artist %next.album|player.remaining=="-00:14" %next.albumartist%\o}

“AAAAA” sits on row 1.

Everything between \n and \o is locked to row 2, no matter how long it grows; overflow becomes an ellipsis or marquee inside that row.

4

I am sorry, I am not a native English user, do not know how to explain my ideal to let you acknowledge, but kimi polished version might useful.If not use just close topic is Ok.

5

Sorry but still very unclear, you have 6 strings and many options to either have them always visible even if empty or not and limit the number of lines and everything. I do not think there’s the need to add something insanely complicated that nearly no one would use.

1 Like