Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Can't easily move "instrument change" elements to different measures #22665

Open
wizofaus opened this issue May 3, 2024 · 6 comments
Open

Can't easily move "instrument change" elements to different measures #22665

wizofaus opened this issue May 3, 2024 · 6 comments
Assignees
Labels
feature request Used to suggest improvements or new capabilities UI Visual issues affecting the UI (not notation)

Comments

@wizofaus
Copy link
Contributor

wizofaus commented May 3, 2024

Issue type

UX/Interaction bug (incorrect behaviour)

Bug description

If you've added a "Change Instr." item to your score, then need to move it to a different measure for whatever reason, there are appears to be no way to do so - dragging/cutting/pasting etc. do not work. This can be an issue if you need to delete measures etc.

Steps to reproduce

  1. Add an instrument change element to the second measure of an empty score
  2. Set properties as needed (e.g. add a frame with a white background so it masks barlines etc.)
  3. Attempt to drag it either to the first or 3rd measure - it won't re-attach itself the way, say, dynamics will.
  4. Select it and "cut" it to the clipboard, then attempt to paste it to another measure, but paste does nothing (edit: unless you only have a single note/rest selected - then it does appear to work. But it definitely doesn't work when cut/copied as part of a range, e.g. if you select the whole measure and cut/copy that to the clipboard).

Screenshots/Screen recordings

No response

MuseScore Version

4.2

Regression

I don't know

Operating system

Windows 11

Additional context

No response

@muse-bot muse-bot added the UI Visual issues affecting the UI (not notation) label May 3, 2024
@zacjansheski
Copy link
Contributor

The same can be said about staff text in general.
Same behavior since Mu3.
Luckily it is easy to cut and paste.

With that in mind I think this should be considered a feature request.

@zacjansheski zacjansheski added the feature request Used to suggest improvements or new capabilities label May 3, 2024
@MarcSabatella
Copy link
Contributor

MarcSabatella commented May 3, 2024

To be clear: cut / paste does work, assuming you select the text itself. Unlike staff text, it doesn’t copy as part of a range, though. Probably by design but I’m not sure.

@wizofaus
Copy link
Contributor Author

wizofaus commented May 3, 2024 via email

@MarcSabatella
Copy link
Contributor

Works for me on Windows and Linux. As with any text, make sure you have a single note/rest selected when pasting.

If you continue to have trouble, please attach the score and give precise steps to reproduce the problem - saying which text you are trying to cut, how you are selecting it, and exactly what you are selecting before pasting it.

@wizofaus
Copy link
Contributor Author

wizofaus commented May 3, 2024

Seems the problem is what you have selected when you pasted - you have to have a note or rest selected (vs a measure/range), then it works.

@wizofaus wizofaus changed the title Can't move "instrument change" elements to different measures Can't easily move "instrument change" elements to different measures May 3, 2024
@MarcSabatella
Copy link
Contributor

By design, yes - text markings like this aren’t attached to ranges, they are attached to specific notes.

Certainly as a feature request, pasting into a range could be interpreted as pasting onto the first note of the selection, or possibly the first note of each staff within the selection, much as was recently implemented for palette add.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature request Used to suggest improvements or new capabilities UI Visual issues affecting the UI (not notation)
Projects
None yet
Development

No branches or pull requests

5 participants