shortcuts for system break and line break don't work

• Jul 14, 2017 - 04:44

Just upgraded from 2.0.3 to 2.1. Preferences still say RETURN for system break and CTRL+RETURN for page break, but the shortcuts don't do anything. The only way I can get the breaks is via the Breaks and Spacers palette.

Windows 10.


In reply to by mike320

Offhand I can't think of a reason for this difference other than "it has always been so". Definitely a useful feature request.

FWIW, I'm not sure how you would currently be selecting measures by keyboard only during this phase of a project. I would imagine that when in these final formatting stages of a piece one would be largely relying on mouse anyhow. So a single click in an empty spot would be the normal way of selecting a measure it seems to me. Curious to hear more about your actual workflow here.

Anyhow, it *is* possible to select barlines by keyboard, using the accessibility features. Define a shortcut for "Accessibility: next element" if one is not already defined (also for previous). Now you can navigate not just notes and rests but also barlines, clefs, time signatures, etc. For now, it's still just "primary" elements - things that live on their own as opposed to being attached to other things. So, notes, but not the articulations or text attached to those notes. Recently this was expanded for 3.0 (by GSoC student divya-urs) to also allow for navigation through most other elements as well. I believe this will be a major step forward is accessibility and usability in general.

In reply to by Marc Sabatella

If I were trying to make a score look identical to an existing score, my desire would be to have the new line entered after the last note of the measure so I could enter my notes, end of this line, press enter, new line is now forced. It would work more like a word processor. MuseScore does this to the point that "word wrap" happens when you have reached the extent that MuseScore can have a certain number of notes on a line, creating a "soft" line break and a "soft" page break as needed.

I don't currently use the shortcuts, because they didn't work in any way that I could figure out to this point.

In reply to by mike320

Ah, interesting, I wasn't thinking in terms of attempting to do layout during note entry. But even so, you wouldn't normally have a measure selected, but instead a note. So that would need to be considered. Also, of course this only covers the cases where you want *fewer* measures per line than fit by default. The converse case would still currently require selecting a measure range, playing with stretch, etc. Which is to say, merely making it so you can hit Enter with a measure selected won't really help that much with this particular use case.

Something else occurred to me: if we allow hitting Enter with a measure selected, what would the expect behavior be if there is only a *partial* measure selected? Or multiple measures?

In reply to by Marc Sabatella

My thought is that if a note is selected, the new line is applied to the measure with the note. So if the measure has only a 1/16th note to start it and filled with rests to the end, enter puts the line break at the end of the measure, and the user can continue to enter his music. The only time I would probably use it is transcribing piano music to keep the measures somewhat line up. Multi instrument music works better in continuous view.

In reply to by mike320

I'd personally use it in lead sheets mostly, as in piano music I am generally much more likely to accept the default layout. But anyhow, it's not a bad idea, and worth submitting an official feature request for. I guess there might be objection that someday we may wish Enter to do something else aside from a line break (like go to Edit mode or whatever, and in fact there is already pending code from divya-urs courtesy of GSoC to allow Enter to apply palette elements), but still it's worth considering.

In reply to by Marc Sabatella

"Offhand I can't think of a reason for this difference other than "it has always been so"."

Just to clarify, it has not always been so. In all my years of using MuseScore since 0.9.6, I don't recall ever selecting a barline to create system breaks or page breaks. Instead, whether using the shortcuts in question or using the palette, I was selecting the measure preceding where I wanted the break to go.

In reply to by [DELETED] 448831

Memory can play tricks, but I can assure, it has never worked to use shortcuts to apply line breaks with a measure selected. I have also used MuseScore since 0.9.6, and while my memory is no more reliable than anyone else, I do have 1.3 portable on my system and tested just now :-). It works the same as it does in 2.1. You can use the *palette* to apply line breaks to either a measure or to a barline, but the *shortcut* of hitting Enter requires a barline. Actually, 1.3 was more limited in that you couldn't apply line breaks by double clicking the palette. I believe this feature was only added at 2.0.2.

In reply to by [DELETED] 448831

It is true the barline appeared to be selected along with the measure in 1.3. But there was no difference in behavior. You still could not create a line break by hitting Enter with a measure selected, even though the barline appears selected. Again, I have it open right in front of me and am testing this. You have to have the barline *only* selected, just as is the case now. This code has not changed in any significant way for over five years.

Similarly, double click simply was not supported for the line break icon prior to 2.0.2, whether you had the barline selected or not. This code was only added for 2.0.2, and I know this because I added it myself, along with support for adding a whole bunch of other element types via double click:…

In reply to by Marc Sabatella

Well, I've officially lost it. After roughly one year away from using MuseScore, I seem to have forgotten everything I ever knew ... or thought I knew.

The sole purpose I can ever recall ever selecting a barline alone was either to make it dashed or invisible.

I apologize for my confusion and the waste of time and energy this thread turned out to be.

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