Double barlines added to individual staves not removed when adding a repeat barline system-wide

• Dec 6, 2014 - 14:20

This has happened to me twice already in the same (fairly new) score. I have attached my score to show the problem.

Mac OS X 10.10.1 NB 83da36c


1. Drag a double barline to the same place on all lines in your score.
2. Realize you meant to put a left hand repeat barline instead (oops).
3. Drag left hand repeat barline to the same place; nothing happens (lines look thicker).
4. Save, close and relaunch Musescore (this has fixed this behavior in the past). No joy.

Work around:

a. Drag single barlines to the same place.
b. Drag left repeat barlines over the singles that you just put in, should take.
c. If new repeat barlines don't show, exit and relaunch Musescore after saving.

See measure 19 of the attached score. I had the same problem with the repeat section that you can see in measure 6 and followed the procedure above to fix.


Attachment Size
I Wanna Be Like You.mscz 7.88 KB



Strange enough it helps if you again drag a double barline into measure 18, then the start-repeat into measure 19.
Also kind of strange things happen fi you drag a start repeat onto measure 11, at rehearsal mark B
the repeats barline does not show up, but the next measure moves to the next page, for no apparent reason.
Did you create that score in that version from scratch?

Confirmed. Reproducible on "My First Score" in a recent Nigthlyt, and Beta1. But this issue is much former. I can reproduce it on a nigthly older than more six months (May 19).

Part of the problem here is the way you added the double bar. You shouldn't have needed to add it to each staff individually, but that's what happens with certain methods of adding barlines. This includes clicking a barline then double clicking the palette icon as well as dragging the palette icon to the barline. Had you added the barline the "correct" way - dragging the barline to the *measure* - then the barline would have been added to all measures at once. And then you'd have been able to change it to a repeat barline just as easily.

As it is, the repeat barline *is* there, but it is being obscured by the double bar lines you have carefully attached to each staff individually. Delete those double barlines and it will reveal the repeat that was there all along.

The problem here, in my opinion, is that it is by no means clear that there is a "right" and "wrong" way to add a double bar, and indeed, the "wrong" way used to work just fine. I mean, I'm very glad there is the ability to override a barline for just one specific staff, but I think it should be not so easy to do accidentally. I think maybe like key and time signatures, it should require Ctrl+drag.

Title Left repeat barline won't "take" if double barline already in place Double barlines added to individual staves not removed when adding a repeat barline system-wide

Ah, only now I understand the instructions from the 1st post, it never occurred to me that you could change individual barlines.
And it doesn't work for any of the repeats barlines, just the others (dashed, dotted, double, end barline, and partly the tick barlines), quite inconsistent, isn't it?

To clarify, my experience was as follows:
With 1.3, in a score for flute solo or other, I get this by dragging and dropping a repeat barline on a double barline (highlighted).
version 1 3.jpg
result 1 3.jpg
With Beta1 (e.g. with "My first Score) and other new and former Nightlies, nothing happens
beta1 result.jpg
(or so, indeed, by removing the double barline, the repeat barline is really present)
result beta 1 after deletion double barline.jpg

Yes, but again, this is only because you added the original double bar (not the repeat) "incorrectly" in the first place. Had you dragged it to the *measure*, it would have been added as a normal double bar, applying to all staves. And then the repeat sign would have replaced it. But it seems you added it as a special one-staff-only override - that's the result of adding it "incorrectly", by dragging to the barline instead of to the measure. And because you added it as a special-one-staff-only override, that override remains in effect even if you change basic barline style to be "repeat".

So there are a few separate issues here worth considering:

1) Most important, I think - these special one-staff-only overrides should not be so easy to create accidentally. I think it should require Ctrl+drag to create them, so people don't continue to make this mistake.

2) It would be worth considering whether adding a repeat barline should clear these special one-staff-only overrides. But I think that's pretty unimportant if we fix #1. Most people will never use those special one-staff-only overrides, so they won't ever encounter this situation, And for the very few people who need to create those special one-staff-only overrides, they might indeed *want* them to remain in effect even if they change the basic barline style.

3)As for why you can't create a special one-staff-only override using the repeat barlines, see Miwarre's response in the issue I linked above #26416: Bar line palette drops only affect some bar line properties. There is *some* rationale for this, I think - at least it seems his response probably applies here as well. It's just non-obvious.

So me being a naive user here, but if I can drag it from the palette to the bar line and it takes, I assume that is the "proper" way to do it. Otherwise, if it isn't working and I start to get agitated, I RTFM and figure out that I am doing it wrong. :-)

Therefore, either:

1) A key combo that you must use to create the unusual situation of different barlines for the same measure in the same score for different parts


2) A dialog box asking "Are you sure?"

to prevent users like me from doing it the "wrong way"...

Status (old) active patch (code needs review)

It seems to me that it would be more logical & consistent to make it so that Ctrl is required for this type of usage - same as key signatures, for example - and so that the basic drop action (including click barline then double click palette icon) will apply the barline to the whole system if possible. And while I don't understand all the ins and outs of how barlines work, it seems it is not hard to accomplish this. Here is a PR:

I guess there will be some discussion over whether there is a good reason it is done the way it is right now. I elected to keep the special casing for "tick" barline styles, but maybe there are cases I am not handling correctly. Still, it seems to work for me, and makes a whole lot more sense than what we do now.

I have been bothered by this for some time, so I'm glad to see this being discussed and to have an opportunity to address this if possible.

Status (old) fixed needs info

The basic issue is fixed in that the "obvious" ways of adding double barlines no longer will create these special single-staff-overrides. You will now need an explict ctrl+drag to create these, just as for key and time signatures. So it is much less likely anyone will run into this problem.

To me, it is still an open question as to whether changing the basic barline type for a system - whether adding an ordinary double bar or a repeat bar - should actually *clear* any existing single-staff-overrides. I elected not to change that behavior, as pretty much everything about these overrides is outside my realm of musical experience. So I feel I have no real insight into what someone who had actual reason to use these might expect. Since the title of the issue now reflects that specific question, I'm leaving it open, but I have marked it "minor" and "needs info".

But to re-emphasize, the specific problem described in the original report is now fixed. Following those steps will no longer prevent the repeat from appearing, because the double barlines you create will no longer be created as single-staff-overrides. Which also means, at step 1, it will no longer appear to be necessary to drag the double bar to each staff individually. The first drag - or click barline then double click palette icon - will add the double bar to all staves simultaneously, just as was the case in 1.3.

Status (old) needs info closed
Status needs info closed
Tags View Changes

Pending discussion happened. Reopen if it is still actual and participants are interested in continuing discussion.