Built-in scratchpad area for editing
I'd like MS to provide a built-in work area for local editing, instead of requiring me to create and later destroy a new empty document.
I am constantly creating new empty scores into which I paste a group of measures to carry out editing that would otherwise affect the entire source score. (Examples: select and delete all notes in a particular voice, switch material to a different voice, merge in a new voice, edit 'note properties' for everything within a phrase to set noteheads, use small notes, etc.)
It would save me a LOT of time if MS provided a built in scratch area. This could pop up at the bottom of the screen, or appear in a separate tab.
The same panel might also be used to display the current content of the clipboard (i.e. switch the panel's view between the clipboard content and the scratch area). (This approach to clipboard visibility might help address requests for enhanced selection tools -- an alternative to manipulating the selection would be to place the selected content in the clipboard, and then then let us edit the clipboard content directly.)
Shortcuts/buttoms could be provided to clear the work area content, exchange it with the clipboard, add/remove staves/measures, and perform other common editing tasks, the need for which would quickly become apparent through use.
A related solution would be to provide a quick one-key way to create a new empty score that matches the content of the clipboard. That would eliminate a whole series of keyboard/mouse actions.
Comments
+1 for this. When I'm writing a big orchestral piece I keep all my scratch work at the end, which is fine for me, but if I want to upload it to musescore.com it doesn't look great. As far as I can tell there's no way to hide a whole section like that.
In reply to +1 for this. When I'm… by benwaffle
+1
... regarding a built-in notational scratch pad.
Otherwise, short of that, the option to put ideas, sketches and variations in a section the that user can choose to hide. Can we hide sections??
Have you already asked for this feature on Github?