Glissandos collide with double-digit start fretmarks in tablature

• Aug 19, 2020 - 11:48
Type
Functional
Frequency
Once
Severity
S3 - Major
Reproducibility
Always
Status
closed
Regression
No
Workaround
Yes
Project

OS: Windows 10 (10.0), Arch.: x86_64, MuseScore version (64-bit): 3.4.2.9788, revision: 148e43f

This has been an issue since the year dot. In MuseScore standard staves, glissandos have a small amount of space on either side to prevent collision with start and end notes:

gliss_standard_staff.png

However, in tablature this space has not been properly implemented:
gliss_tablature_1.png

If there is a double figure at the start, there is a collision:

gliss_tablature_2.png

Probably, this is connected with #110981: Glissandos not centred between notes in tablature.


Comments

After seeing that my issue was a duplicate, I decided to take a look at the code, I notice that there's no specific instance of tab-width but that the code only deals with the "notehead" width. If I merely add a line of code to reset the x-offsetting to take into consideration the "tab" width only on the first (left most) position of the glissando when on a tab-staff, it seems to fix the issue. I'll do a PR and hope some will be willing to further test it.

In reply to by geetar

@geetar, please test out a nightly branch now, as this PR i put together includes updating the alignment of the glissando lines besides making sure they don't clash with double-digits. Left-sided and Right-sided portion of the lines should be equivalent now. If you catch anything funny, post a comment etc, but it should be okay.

OS: Windows 10 (10.0), Arch.: x86_64, MuseScore version (64-bit): 3.6.0.395303918, revision: github-musescore-musescore-

Looks fine.

Fix version
3.6.0