Improvements to the splash screen
The MuseScore splash screen is rendered using two pre-rendered images, one for low-resolution displays and another for high-resolution displays.
This has the following consequences:
-
The splash screen looks mostly fine on displays that happen to match the exact DPI resolution of the two pre-rendered images, but for anything in between, it ends up looking blurry and/or blotchy. This does not make a good first impression on users.
-
The pre-rendered image files are somewhat large and increase the size of the MuseScore binary distribution by ~1.4 MiB.
-
The pre-rendered images contain “burned-in” text containing the current MuseScore version. That means that the images need to be updated by a designer every time a new version of MuseScore is released.
-
The “burned-in” text on the pre-rendered images is rendered using a font called SFProDisplay. This is an Apple system font that looks out of place on Windows and Linux and also clashes with the font used for the status messages that are displayed in the middle of the splash screen.
-
The splash screen no longer has a special design for developer builds as it used to in older versions of MuseScore.
This problems can all be solved by rendering the splash screen on the fly using vector-based graphics instead of using pre-rendered images.
Comments
PR #6187.
Fixed in branch 3.x, commit a6934413fa
_Fix #306512: Improvements to the splash screen
Rewrote the splash-screen code so that it renders everything on the fly using vector graphics instead of using pre-rendered images.
Also designed and implemented a darker version of the splash screen that is automatically used for unstable/development builds._
Fixed in branch 3.x, commit aaba461e1e
_Merge pull request #6187 from Spire42/306512-improvements-to-the-splash-screen
Fix #306512: Improvements to the splash screen_
Fixed in branch 3.5beta, commit 9b50600c4c
_Merge pull request #6187 from Spire42/306512-improvements-to-the-splash-screen
Fix #306512: Improvements to the splash screen_
Automatically closed -- issue fixed for 2 weeks with no activity.