Make name of Text style more visible in the Properties toolbar

Open
#16,844 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
42/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
cpp
Domain
design, desktop

Research direction

Start by reviewing the Text tab and Properties panel behavior described in the issue, alongside the related Position request in #16664. Done means Text Style is permanently visible in the Text section, with the proposed More-button changes resolved consistently without making the novice workflow harder.

Written by the indexing model from the issue text.

Description

feature request needs design
Your idea

Text Style is currently hidden away behind the More button in the Text tab of the Properties panel.

IME, it would improve workflow if Text Style were made more permanently visible in the Properties panel by moving it into the Text section itself.

Problem to be solved

IME, it is often necessary to be able to view and change text style of an element. For example:

  1. To double-check that an element has the correct style
  2. To confirm the style whose property you are about to change (and perhaps set as default for the style)
  3. When changing text styles, for example LH guitar fingering to Fingering. In this case you may also need to change the offsets of the element – with the current UI this requires the use of two different More buttons.
Additional context

I've also made a request for Position to be moved from the More button into the Appearance tab – see #16664. If these two features were implemented it might also allow the More button to be dispensed with altogether and its properties made permanently visible under Text. IMV, this would not affect ease of use for the MuseScore novice.

Dominant language
C++
Stars
15.1k
Forks
3.3k
Avg merge
2d 2h
Merged PRs (30d)
91

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from musescore/MuseScore

All issues in musescore/MuseScore

Similar issues

More C++ issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.