Tie command does not properly handle chords with unisons

• Aug 17, 2019 - 17:56
Reported version
3.2
Type
Functional
Frequency
Once
Severity
S4 - Minor
Reproducibility
Always
Status
PR created
Regression
No
Workaround
Yes
Project

In any score

Enter a note
Add an unison note (press alt+1)
Add a tied chord by pressing +
Select the measure with these notes and press ctrl+down (or up) arrow
Result: 3 out of 4 notes change octaves as expected.
Expected: all notes change octave

Now select the note that did not change octaves and press ctrl+ up (or down) arrow and see the same notes as before change octaves.

Workaround

Delete the stray note and reenter it where it belongs. You can move it after you reenter it.


Comments

The real problem is in the creation of the tied unisons. Currently that is not handled correctly, causing weird behavior such as this.

For now, the easiest way to create properly tied unisons is to do the following:

Enter a note
Add an octave note
Add a tied chord by pressing +
Press ctrl-down

Now that the chords are tied together properly, if you select the measure and press ctrl-up or ctrl-down, all notes will change octaves as expected.

We could however create and maintain a page with known bugs and their workarounds and link to that from the handbook.
The 'maintain' part is worrying be though...

Ideally, the person who adds a certain workaround to the page would post a comment on the issue. When the issue is fixed, that person will get a notification, and will know that the workaround can be removed, unless someone else removes it first.

create and maintain a page with known bugs and their workarounds

That's what we do daily in the forums and issue tracker.

indeed, I closed that other one as a duplicate

That's what we do daily in the forums and issue tracker.
yes, but not in a single page, instead scattered all over the place