Impossible to delete a custom barline

• Mar 12, 2013 - 13:19
Type
Functional
Severity
3
Status
closed
Project
MuseScore

Steps:
1- Create a new score;
2- Drag a barline (Palettes -> Barlines) different from repeat barlines or normal barline (for example Double Bar line) onto one barline in the score: drop the new barline only when the original barline is highlighted in red (NOT when the measure containing the barline is highlighted);
3- Select this barline;
4- Hit canc, or right-click + cut, or Ctrl+x (Windows);
5- Nothing happens.

Expected results:
- The barline is deleted and replaced with a normal barline

Musescore Nightly build revision a3c9bc1
Windows XP Professional SP3

Notes:
- If the same steps are performed, but the barline is dropped onto the measure, everything works as expected.

- Workaround: drag and drop a simple bar over the barline.

(Marking as minor since a workaround exists)

Comments

• Mar 22, 2013 - 23:49
Severity ⇒
Status (old) fixed ⇒ active

The fix actually removed the possibility to customize an individual bar line.

I believe it should be reverted and a different one implemented (I'm working on it).

M.

Reply

• Mar 23, 2013 - 11:45
Severity ⇒
Status (old) active ⇒ patch (ready to commit)

Well, in this case the regression affected the UI: a specific 'gesture' (dropping a palette item on a specific element) was no longer routed to the right method.

Given the current test framework, I don't know if a test for this can be made reliably: changing the element programmatically may easily not reveal any problem even if the UI is actually broken.

Anyway, I have a fix ready: https://github.com/musescore/MuseScore/pull/272

Thanks,

M.

Reply

• Mar 23, 2013 - 19:05

I had the same doubt and I couldn't find an answer.

Currently, [Del] resets any custom style (i.e. style different from measure end bar line style), but does not reset a custom span (i.e. a span different from staff span setting). In other words, if a bar line is 'different from the others', [Del] regularizes it to its measure default but not to its staff default. I have the feeling that the latter is a 'stronger' customization than the former and a 'stronger' action should be required to remove it.

Other opinions about this, anyone?

Thanks,

M.

Reply