Great success writing book-like score in 3.1!

• Jun 13, 2019 - 00:42

I just completed a fairly extensive tutorial ( https://musescore.com/bsg/bwv582_57ff ) in flowing vertical-block paragraphs in MS 3.1 without a single crash or misbehavior (AFAICT). The previous version would crash every fourth or fifth time I adjusted a vertical-block height or pad in the inspector. Those bugs have really been found and fixed, and version 3 is now working really well. Congrats!


Comments

Fantastic job, well done! Entering this much text in MuseScore is not easy. Hopefully we'll get some more formatting tools at some point (e.g. line breaks and justification) but you've coped well enough without them.

In reply to by shoogle

Thanks. "Enter a paragraph at a time, save after each paragraph, default the top/bottom pad, and it goes like a run of sixteenth notes." I could write another tutorial on doing this sort of thing (interposing music examples is harder)....

In reply to by BSG

I've noticed that too. It's a tricky one to deal with, and it applies to images as well as text. Perhaps clicking on the frame border (the blue line) should always select the frame rather than its contents, even if they overlap.

In reply to by BSG

The rule? If you have several things displayed stacked on top of each other, ctrl+click will change what is selected. If there are more than 2 things, repeat until you get the right item. Sorry, that's the best rule I can give you. Marc made this and could explain it better, but it's probably related to the z-order and you won't know the z-order of an item until it's selected so knowing in inner workings probably won't help.

My second rule of using this, if you are using this to select an item stacked on something else. It's probably not a good idea to rely on this to add it to list selections (several dynamics for example). Just be happy you got the right one and do what you need to it and use the list selection for the other items.

In reply to by mike320

More generally, Ctrl+click cycles through all the elements that exist at the clicked location before deselecting. Prior to this change (3.0.1 or something maybe?) Ctrl+click added an element to selection, then another Ctrl+click removed it. That's still the case, actually, and if there aren't overlapping elements where you clicked, there is no change at all. But if the are overlapping elements, say A, B, and C, then previous repeated Ctrl+click would give you A, nothing, A, nothing, A, nothing, A, nothing.... Now it gives you A, B, C, nothing, A, B, C, nothing. Just as before if there are already selected elements elsewhere, they remain selected - this is about adding and removing elements from the selection.

As for the actual order, it's the z-order (aka stacking order) mostly indeed - the same order used to control which order is drawn on top of which. This is normally predetermined by the element type, unless you override it in the Inspector. If f two elements have the same type, then I also check voice to try to make it so the thing you get on first click is what you want most of the time.

But the bottom line is, if you find an element hard to select because it is underneath something else, Ctrl+click now comes to the rescue.

Do you still have an unanswered question? Please log in first to post your question.