Edit behavior: Chord offsetting isn't performed in Voice-3 in edit mode sometimes
Reported version
3.3
Type
Functional
Frequency
Once
Severity
S4 - Minor
Reproducibility
Always
Status
by design
Regression
No
Workaround
No
Project
Open up this mscz file with one measure and attempt edit-mode [ctrl+e] and chord-offsetting with the [left/right arrow keys]. What is going here? The note heads individually move, save for one chord or so (as read in the provided staff-text), rather than the expected chord-offsetting.
Strangely, it doesn't always happen: there are instances when voice-3 moves just fine as regularly expected, so I'm not sure what the actual "trigger" is. It's not merely the use of voice-3 that does this. Hopefully gets figured out by someone.
| Attachment | Size |
|---|---|
| edt_move_multivoice.mscz | 5.35 KB |
Comments
This appears to be working exactly as designed. If the chord contains only one note, then the offset is applied at the chord level. If the chord contains multiple notes, then the offset is applied to only the note that is being edited.
Absolutely. Edit mode on a single note is supposed to move that note only. There is special-casing for single note chords where it gets converted to a chord offset instead since that is the more likely use case. But in general, the expected way to move an entire chord is with the Inspector.
In reply to Absolutely. Edit mode on a… by Marc Sabatella
Hrm, I'm slightly surprised that a single note moves as a whole chord, but a triad for instance moves merely one of its noteheads in edit mode.. I suppose the developers have their reasons. Thanks for clarifying that this is intended rather than an oversight.
I was hoping that, for instance, I could offset one chord from another voiced chord by using this quick 'shortcut', but it sounds like this isn't intended to do so and will need to continue using the usual Inspector chord-offset behavior instead. Sorry for the false alarm ;) . . . probably should've asked this in the forum first.