Make pasting into blank bars work the same as pasting into bars with content
To reproduce:
- Somewhere in the middle of your piece: Menu - Add - Measures - 4 - Ok
- Copy any four bars of content
- Select the new 4 bar rest of measures that have just been created
- Paste the content into them
Expected:
- The bars remain selected, the new content appears, the screen doesn't move
Actual:
- The screen jumps back to the start of the piece, a massive number of bars not related to the pasting are selected
Comments
Please post a sample score exhibiting this issue, also stating what version of MuseScore and what OS (i.e your operating system).
I followed your instructions, and copy/paste works fine. (MuseScore 2.1, Windows 10)
Regards.
Musescore 2.1.0.871c8ce
Windows 10 updated on 2018/01/17
In reply to Musescore 2.1.0.871c8ce… by Richard Cooke
Where to add the 4 blank measures and what measures to copy/paste into those added blank measures?
I can successfully copy/paste in 'Continuous View', although the score does jump to the beginning.
Also, what happens for you in 'Page View'?
Precise step by step instructions to reproduce the problem would still be helpful, but I think I can guess what you are referring to. If you have a multimeasure rest and try pasting into it, the measures that existed originally no longer exist - they have been converted form multimeasure rest to standard measures. So it is impossible to manage the selection in the same exact way as in the usual case. True, it would be nice if we clould handle this more gracefully, but the current behavior is better than crashing, which is a problem we used to have that was fixed by disabling the selection :-)
Anyhow, the issue is not about whether the measures are empty or not, but about whether multimeasure rests are turned on. Really, there is no reason for them to be turned on in this (or any) score, so the simple solution is to press "M" to tuirn them off. Multimeasure rests are intended for parts, not full scores.
In reply to Precise step by step… by Marc Sabatella
I wasn't aware of M. Thanks, though the bug still exists that solves the problem for me.