In tablature, if "Show rests" is unchecked, the hidden rests still obey collision avoidance rules: may result in larger than expected vertical spacing
Reported version
3.2
Priority
P2 - Medium
Type
Functional
Frequency
Once
Severity
S3 - Major
Reproducibility
Always
Status
active
Regression
Yes
Workaround
Yes
Project
MS 3.2.3
Open the attached score and look at the bottom of page 2. The last system on the page is not lined up correctly with the last systems on other pages because rests in Tablature are still being counted as part of the skyline—despite the "Show rests" option being unchecked in Staff Properties.
This wasn't a problem in MS2.
Attachment | Size |
---|---|
system_distance.mscz | 29.31 KB |
Comments
Confirmed. A workaround, such as it is, would be to mark the rests invisible .
This ordinarily wouldn't cause such a noticeable difference, but on this score, the "Music bottom margin" has been set unusually low. Generally, if you want an even bottom margin, you'll be better off keeping closer to the default with this setting. But the bad skyline will also affect markings below the staff.
Not sure if the better fix is to override addToSkyline() for rests so they can check the status of the staff property, or maybe to not generate the shape for the rest at all. The latter would possibly have other effects as well, but they might be good - eg, there may well be other respects in which these rests are affecting layout adversely.
This issue also affects the spacing between staff and tablature within a system: e.g. measures 15-19 in the attached score. The workaround is to select the tablature staff in the affected system and apply Ctrl + R to reset the (invisible) rests.
Still present in 3.4.2.
Updated workaround: (1) Check "Show rests" (Staff properties > Advanced style properties > Note values; (2) select all rests in tab and press "V" to make invisible. (2) Uncheck "Show rests" (Staff properties > Advanced style properties > Note values.
Related to #270551: [EPIC] Tablature issues.
Bump.
In reply to The default position of… by geetar
Thanks for bumping this geetar.
Indeed, I've bumped my head on the issue!
scorster