Skip to content

Let status OSD messages use available screen width - #9260

Open
kevinherron wants to merge 1 commit into
omacom:quattrofrom
kevinherron:fix/osd-message-width-from-screen
Open

Let status OSD messages use available screen width#9260
kevinherron wants to merge 1 commit into
omacom:quattrofrom
kevinherron:fix/osd-message-width-from-screen

Conversation

@kevinherron

@kevinherron kevinherron commented Aug 30, 2026

Copy link
Copy Markdown

Status OSD messages currently cap text at 190sp. This truncates long application names and audio output descriptions even when wider displays have plenty of room.

This sizes status-message text from the output width, allowing the card to grow to at most half the screen while preserving 190sp as its minimum cap. Media OSDs retain their fixed width because track metadata is unbounded and changes frequently. The card now derives its frame and row insets from BorderSurface, so the width calculation and rendered chrome use the same geometry.

Before

Launch message:

Status OSD truncating a long application name

Audio sink message:

Status OSD truncating a long audio sink name

After

Launch message:

Status OSD showing a longer application name

Audio sink message:

Status OSD showing the complete audio sink name

The progress OSD remains compact:

Compact progress OSD

Deliberately overlong status text still elides at the half-screen ceiling:

Status OSD respecting the half-screen ceiling

A status message was cut off at a fixed 190sp, so a long app name or
audio sink description elided on an ultrawide with room to spare. Bound
it by half the output width minus the card's chrome instead, keeping the
old width as a floor for narrow screens.

Media OSDs keep their fixed cap: track metadata is unbounded and changes
on every track, and the card should not resize with it.

The card's frame comes from BorderSurface's padding and content insets
now, so its width, height, row margins, and the cap's chrome share one
definition instead of each adding `pad` to the borders by hand.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant