search

musescore / MuseScore

MuseScore is an open source and free music notation software. For support, contribution, bug reports, visit MuseScore.org. Fork and make pull requests!
https://musescore.org
Other
12.08k stars 2.6k forks source link

Tempo marking palette items are not resizeable #22082

Open Riley-Sullivan opened 5 months ago

Riley-Sullivan commented 5 months ago

Issue type

UX/Interaction bug (incorrect behaviour)

Bug description

You can't resize palette items that have a note in them.

Steps to reproduce

  1. Expand the “Tempo” palette.
  2. Right-click “quarter = 80” and choose Properties.
  3. Increase “Content scale” to 1 and hit OK.
  4. See error: “quarter = 80” does not get any bigger.
  5. Now right-click it again and choose Properties again. Note that “Content scale” didn’t change (it is back to 0).

Screenshots/Screen recordings

https://github.com/musescore/MuseScore/assets/163907533/84279dde-7c64-400b-b25b-4aab7e502da3

MuseScore Version

4.2.1

Regression

Yes, this used to work in MuseScore 3.x and now is broken

Operating system

macOS 12.7.2

Additional context

No response

zacjansheski commented 5 months ago

The default is zero for that element.
@avvvvve @mathesoncalum FYI

avvvvve commented 5 months ago

@mathesoncalum whenever we get around to this one...

One issue here is that, for all of the tempo palette elements that are of the form "note value = #" or "note value = note value" (i.e. anything that's not text), the "Content scale" in properties is set to 0. This is making it impossible to be resized. We should replace the 0 with whatever value keeps them visually the same size as they are now, and hopefully fixing this will allow users to resize them again.

The second part is dragging any of these same " = " elements from the "More" menu into the palette doesn't always work. The "Add to Tempo" button is not functional either. Perhaps this can be fixed here too? :)

https://github.com/musescore/MuseScore/assets/20806406/8ed33e16-55c0-4000-a646-4cb0e70e9629

mathesoncalum commented 5 months ago

One issue here is that...

Copy that!

The second part is...

Cool, I'll address this when I get round to #18417