Skip to content

Instrument descriptions get cut off in New Score dialog #27891

@shoogle

Description

@shoogle

Issue type

UI bug (incorrect info or interface appearance)

Description with steps to reproduce

When an instrument description is too long to fit on one line it gets cut off.

  1. File > New > Choose instruments (or press I in an existing score).
  2. Search for "Violone" and click on it.

Current behaviour: The description gets cut off at the end of the line.

Expected behaviour: It should go onto a second line (or employ one of the animation techniques discussed below).

Supporting files, videos and screenshots

Image

What is the latest version of MuseScore Studio where this issue is present?

Latest nightly master

Regression

Yes, this used to work in a previous version of MuseScore 4.x

Operating system

Windows 11

Additional context

In the original design for the Instruments dialog, instrument descriptions were allowed to go onto a second line. I'm pretty sure that worked when it was first implemented, hence this is a regression.

Sometimes a second line might not be enough, either in English or in one of the translations. In this case, the text could be displayed on a single line with a sideways scrolling animation, like a dot matrix display. Alternatively, it could be displayed on multiple lines with a vertical scrolling animation, like movie credits.

If the mouse cursor hovers over the text, the animation would pause, and the user could scroll the text manually with the mouse wheel or touch gestures. If the mouse is cursor is moved away again then the animation would continue.

(If anyone is worried about animations being distracting, it's worth remembering that, for the vast majority of instruments, the description is short enough to fit on one line, so no animation is needed.)

The solution adopted here for instrument descriptions should be re-useable for descriptions of percussion sub-instruments in the new percussion specification.

Checklist

  • This report follows the guidelines for reporting bugs and issues
  • I have verified that this issue has not been logged before, by searching the issue tracker for similar issues
  • I have attached all requested files and information to this report
  • I have attempted to identify the root problem as concisely as possible, and have used minimal reproducible examples where possible

Metadata

Metadata

Assignees

Labels

UIVisual issues affecting the UI (not notation)communityIssues particularly suitable for community contributors to work onregression MS4Regression on a prior release

Type

Projects

Status

In progress

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions