Cannot drop pedal and other lines onto element in voice other than 1
Reported version
3.4
Priority
P2 - Medium
Type
Functional
Frequency
Once
Severity
S4 - Minor
Reproducibility
Always
Status
active
Regression
No
Workaround
Yes
Project
Steps to Reproduce error
1) Insert a whole note element in a measure in 1st voice.
2) Insert several note elements (quarter, 8th, etc) in the same measure in another voice.
3) Try to "attach" several different line elements (hairpins, pedals, 8va, trill to the second voice elements). Musescore will not let you.
Attached pic shows me trying to attach an octave (8va) element to several second voice notes.
Comments
HOw are you trying to add the line? For me it works as expected if I select the range of notes in voice 2 then click the palette icon. It also works to attach to just the first note then adjust the handle.
If you have a case where you can't get it to work, can you attach the specific score and more precise steps?
In reply to HOw are you trying to add… by Marc Sabatella
OK, I can confirm that if I select a range and double click on the palette element it does work. However, it does not work if I drag and drop on the first note I want the element to affect, which is how I ALWAYS do it and other elements work fine doing it that way. I included the section of music I want to add an octave on the last sextuplets of each measure in measures 117 - 120. BTW: it also has a problem with hairpins and pedal elements and others in the "Lines" palette. Oddly, no problem with slurs, which is another "range" element. Tested elements in other palettes - ornamentions, articulations, grace notes. They work as intended.
Thank you for your help.
Well, a line needs a start and an end, so doesn't really apply to a single element
In reply to (No subject) by Jojo-Schmitz
JoJo, FYI: I was noticing that on version 3.4 I also had this issue.
In reply to Well, a line needs a start… by Jojo-Schmitz
Agreed; however, there is no prob with slurs.
Drag and drop is almost always less efficient than simply clicking, FWIW. But I can confirm you cannot drop onto a note in voice 2. If you wish to use drag & drop, you would have to move the start point as well. So that's a workaround also.
Looking at the code, it appears it has always been this way - only voice 1 is considered in ScoreView::dragTimeAnchorElement(). Probably it would actually work to check each voice in turn to see if there is something there.
(it was reported against 3.x development version, although as I said, I believe this goes back a long ways).
OP confirmed it to be in 3.4.2 too
In reply to Drag and drop is almost… by Marc Sabatella
Thank you Mark for looking at this. Would you agree that there is at least an inconsistency with how elements work. As I stated earlier, the slur works fine with drag and drop as do other elements. It appears a minority of elements, though most of the "line" palette, do not allow drag and drop onto a voice other than voice 1. i couldn't tell from your comment whether this will be fixed in a later 3.5 version or, since there is a workaround, it will not be fixed. IMO, inconsistency in how something works should be fixed.
I did not actually check to see if it happens with 3rd or 4th voice, but it prolly does.
It is not a bug (it it is one at all) introduced by 3.5, and as we're already at a 3.5 Release Candidate only (reasonably bad) regression would get fixed for 3.5 Final.
This issue here might get fixed though for 3.5.1...
To be clear: I do agree it's a bug, and probably quite fixable. But as mentioned, between a release candidate and the actual release one normally fixes only regressions - bugs that were actually introduced in the new release. The idea is to reduce risk by only fixing the most critical issues, since every change introduces the risk of breaking something else.
No reason a fix could not be considered for 3.5.1 or some other future release, though. Meanwhile, as mentioned, there are several ways to get the job done already.
In reply to To be clear: I do agree it's… by Marc Sabatella
Sounds good. Thanks.