Setup assistant window cut off

• Oct 11, 2019 - 15:36
Reported version
Graphical (UI)
S2 - Critical

I'm reporting this issue for the 3.3 release candidate but I've observed it in previous versions. macOS 10.11.6 on MacBook Pro with a 1280x800 screen resolution. Also, MuseScore starts with the German localisation but I don't know whether that makes a difference.

When I start MuseScore for the first time or after having reset preferences to default, the setup assistant window is too large to fit the screen's width. This results in not being able to the "Continue" button without resizing the window or moving it further left.

I think a fix for this issue should be prioritised as any new user of MuseScore who runs into it will get a poor first impression of the programme.

Bildschirmfoto 2019-10-11 um 15.29.45.png


Well possible this is due to missing line breaks in the German translation of that text (the English text has one)
I've added some now (two, the German text is quite a bit longer than the English), so the next version, may not have that issue anymore.

Not sure whether this dialog can get triggered again after having done a translations update? It so, this could get tested now

Actually that does seem to be possible, please try the following:

  1. Update translations (Edit > Preferences > General > Language > Update translations
  2. Tick at application/startup/firstStart in Edit > Preferences > Advanced set a tick at application/startup/firstStart
  3. Restart MuseScore
Status active fixed
Fix version 3.3.0

I tried this on Windows 7 and that dialog is much narrower now, so I regard the issue fixed, at least for German.
I'll leave a hint for the translators about this.

Thanks for bringing it up!

Thanks a lot, @Jojo-Schmitz. That did work and that way the issue is resolved for German.

Would it be possible to add size constraints to the window itself so that translators don't need to add line breaks?

I've check a couple other translations, they all should work.

But yes, having an auto-wrap in that dialog might help to prevent this again.
That would rather be a Suggestion though, and probably better separate from this bug report?

Fix version