Continuous view: white block appears when wallpaper changed from default to PNG image
Reported version
3.0
Priority
P1 - High
Type
Graphical (UI)
Frequency
Many
Severity
S4 - Minor
Reproducibility
Always
Status
closed
Regression
No
Workaround
No
Project
In continuous view, staff names appear correctly when scrolling through the score, as with the first image. However, switching the paper (Preferences > Canvas) from a standard color to one of the wallpaper PNG files creates an opaque block to the right of the staff names, as in the second image. The block appears to be connected to the staff names, as it remains in the same place as one scrolls through the score.
Fix version
3.5.0
Comments
Came up again in #283038: Blank spot in continuous view
Came up again in https://musescore.org/en/node/287041
Came up again in #287849: Continuous View Instrument List Bug
and again in https://musescore.org/en/node/289872
relates to #272135: [EPIC] Continuous view issues
https://github.com/musescore/MuseScore/pull/5255
Again in #297330: Bug Affichage
And another time in #297597: DISPLAY BUG IN Linear view
https://github.com/musescore/MuseScore/pull/5599
again in {#300647]
Fixed in branch master, commit 6645a88912
_fix #279877: Continuous view: white block appears when wallpaper changed from
default to PNG image
Solved by enabling transformation matrix for tiled pixmaps.
Also, replaced the call to setMatrixEnabled() by a call to setWorldMatrixEnabled()
in ScoreView::paint(). Reason is setMatrixEnabled() is now an obsolete QT method
and and is replaced by setWorldMatrixEnabled(). And as a matter of fact,
setMatrixEnabled() is just a call to setMatrixEnabled()._
Fixed in branch master, commit 10cde4d6ff
_Merge pull request #5599 from njvdberg/issue-279877-white-gap
fix #279877: Continuous view: white block appears when wallpaper chan…_
Fix version 3.5.0 again, @Jojo-Schmitz?
Automatically closed -- issue fixed for 2 weeks with no activity.
In reply to Auto close by System Message
I'm getting this same issue.... "It's backkk."
re you having it with the nightly builds for 3.5? That's the first version with the fix, according the comments above.
Issue is solved in nightly 3.5 builds since halve February. So you need a recent 3.5 nightly build or wait until release of 3.5.