The trill glissando line has a poor rendering cadiz1 • Jul 13, 2015 - 13:47 Type Functional Severity S4 - Minor Status closed Project MuseScore Nightly 096e59f/ Windows 8.1 All is said in the title. Poor rendering in the palette and in the score. See the comparison between the 2.0.1 (trill glissando vs. wavy line in Line palette) and the last Nightly: Reply Comments [DELETED] 5 • Jul 13, 2015 - 13:49 The wavy line does look better! Reply cadiz1 • Jul 13, 2015 - 13:50 Indeed. Notice also the "g" of glissando collides the trill line with the last Nightly Reply [DELETED] 5 • Jul 13, 2015 - 13:52 It's again Windows only. 2.0.1 on the left, self build 20f9a2d30b on the right on Mac OSX Reply cadiz1 • Jul 13, 2015 - 14:58 - On May 5 , I receive this (like 2.0.1). As expected (in the score and the palette) - On May 6 , I get: A side effect of this commit ? : https://github.com/musescore/MuseScore/commit/eff562ee3f6803ef0decaca0d… - On May 7 , slight improvement of the rendering - the collision is less pronounced - in the score, but not in the palette ("strange" always) This commit maybe? https://github.com/musescore/MuseScore/commit/f6b88f13957383284ecb5374a… - And on May 8 , I receive the current result: This one ? : https://github.com/musescore/MuseScore/commit/3e383af34578c7bf21b767b12… or/and less likely the immediate following commit?https://github.com/musescore/MuseScore/commit/7fbf11fd4ebb5168002f7d4f2… Reply Git Message • Jul 13, 2015 - 16:57 Status (old) active ⇒ fixed Fixed in branch master, commit c0bb98b04a ugly fix #68846: The trill glissando line has a poor rendering Reply Git Message • Jul 13, 2015 - 16:58 Fixed in branch 2.0.2, commit 1b414cd1dd ugly fix #68846: The trill glissando line has a poor rendering Reply cadiz1 • Jul 13, 2015 - 18:28 Rendering more "clean" , thanks for quick fix. Just regret a little the "g" which continues to touch the line. Don't know if this deserves to report this? Reply System Message • Jul 27, 2015 - 18:35 Status (old) fixed ⇒ closed Automatically closed -- issue fixed for 2 weeks with no activity. Reply
cadiz1 • Jul 13, 2015 - 13:50 Indeed. Notice also the "g" of glissando collides the trill line with the last Nightly Reply
[DELETED] 5 • Jul 13, 2015 - 13:52 It's again Windows only. 2.0.1 on the left, self build 20f9a2d30b on the right on Mac OSX Reply
cadiz1 • Jul 13, 2015 - 14:58 - On May 5 , I receive this (like 2.0.1). As expected (in the score and the palette) - On May 6 , I get: A side effect of this commit ? : https://github.com/musescore/MuseScore/commit/eff562ee3f6803ef0decaca0d… - On May 7 , slight improvement of the rendering - the collision is less pronounced - in the score, but not in the palette ("strange" always) This commit maybe? https://github.com/musescore/MuseScore/commit/f6b88f13957383284ecb5374a… - And on May 8 , I receive the current result: This one ? : https://github.com/musescore/MuseScore/commit/3e383af34578c7bf21b767b12… or/and less likely the immediate following commit?https://github.com/musescore/MuseScore/commit/7fbf11fd4ebb5168002f7d4f2… Reply
Git Message • Jul 13, 2015 - 16:57 Status (old) active ⇒ fixed Fixed in branch master, commit c0bb98b04a ugly fix #68846: The trill glissando line has a poor rendering Reply
Git Message • Jul 13, 2015 - 16:58 Fixed in branch 2.0.2, commit 1b414cd1dd ugly fix #68846: The trill glissando line has a poor rendering Reply
cadiz1 • Jul 13, 2015 - 18:28 Rendering more "clean" , thanks for quick fix. Just regret a little the "g" which continues to touch the line. Don't know if this deserves to report this? Reply
System Message • Jul 27, 2015 - 18:35 Status (old) fixed ⇒ closed Automatically closed -- issue fixed for 2 weeks with no activity. Reply
Comments
The wavy line does look better!
Indeed.
Notice also the "g" of glissando collides the trill line with the last Nightly
It's again Windows only.
2.0.1 on the left, self build 20f9a2d30b on the right on Mac OSX
- On May 5 , I receive this (like 2.0.1). As expected (in the score and the palette)
- On May 6 , I get:
A side effect of this commit ? : https://github.com/musescore/MuseScore/commit/eff562ee3f6803ef0decaca0d…
- On May 7 , slight improvement of the rendering - the collision is less pronounced - in the score, but not in the palette ("strange" always)
This commit maybe? https://github.com/musescore/MuseScore/commit/f6b88f13957383284ecb5374a…
- And on May 8 , I receive the current result:
This one ? : https://github.com/musescore/MuseScore/commit/3e383af34578c7bf21b767b12…
or/and less likely the immediate following commit?
https://github.com/musescore/MuseScore/commit/7fbf11fd4ebb5168002f7d4f2…
Fixed in branch master, commit c0bb98b04a
ugly fix #68846: The trill glissando line has a poor rendering
Fixed in branch 2.0.2, commit 1b414cd1dd
ugly fix #68846: The trill glissando line has a poor rendering
Rendering more "clean" , thanks for quick fix.
![glissando.jpg]( "glissando.jpg")
Just regret a little the "g" which continues to touch the line. Don't know if this deserves to report this?
Automatically closed -- issue fixed for 2 weeks with no activity.