I haven't seen the the code yet, but I guess version 3.0 can't read the manually changed position and set the default position, which is vertically centered to the staff.
Which it is not in the image...
Are they set "fixed to line" (like they should)?
Anyway, I see now they are not in 2.x, so 3.0 is fine here
Ah, now I see what our mean with user setting, this is about the chord symbols, not the slashes
Comments
relates to #274863: [EPIC] Importing <= 1.14 version scores to 3.0
You mean chords symbols, don't you?
In reply to You mean chords symbols, … by Jojo-Schmitz
Yes. Rename the title
Aren't those slash notes supposed to be vertically centered to the staff?
In reply to Aren't those slash notes… by Jojo-Schmitz
I haven't seen the the code yet, but I guess version 3.0 can't read the manually changed position and set the default position, which is vertically centered to the staff.
Which it is not in the image...
Are they set "fixed to line" (like they should)?
Anyway, I see now they are not in 2.x, so 3.0 is fine here
Ah, now I see what our mean with user setting, this is about the chord symbols, not the slashes
That (superfluous) bass clef though seems misplaced
In reply to That bass clef though seems… by Jojo-Schmitz
This superfluous bass appears in 2.3.2 and 3.0. In 1.3 version which is used to create score there is no superfluous bass.
OK, I've seem that happening before. But now in 3.0 it additionally is in the wrong place.
relates to #272132: [EPIC] Text positioning issues. If source score is 1.14, we don't have to keep elements position in 3.0.