Musescore 2.0.2 Always Minimized to Toolbar if Hide Toolbar Option Selected

• Feb 22, 2016 - 22:16
Graphical (UI)
S4 - Minor
by design

Windows 10 with Chrome. Opened Musescore as usual from any method allowed, and the task simply stays on the toolbar no matter how many times you click it. The task opens and there is a miniature on the toolbar of the score I'm using, but it will not opened. Ran a repair-- no joy. Reinstalled, no joy. Finally, I thought, this image is nearly a full image of Musescore, just too small. So I turned off the hide show toolbar option on hover (I'm on an HP Spectre Ultrabook). BAM, Musescore showed up immediatly at normal non-full screen size. I am current on Windows 10, I am sure.

GIT commit: f51dc11


if you execute via command line with " -F" then do you still have problem with hide toolbar? (Sometimes mscore is just off screen, which would explain why you still see the mscore task in the toolbar).

Status (old) active by design

Yes, the problem clearly was that it was off screen. It works with or without autohide toolbar on, as long as you shut down with Musescore visible. "MuseScore.exe" -F also works although it does not maxiumize the Musescore window-- you must do it. (-F must also be outside the quotes in Win 10 wierdly not your problemo)

Please close, though I think it would be wise to consider showing some part of the MuseScore window on restart, I guess that is a minor issue.

You are not the first one to run into an issue where musescore window gets offscreen and user doesn't know what is going on.

But unfortunately, musescore is adjusting it's screen offset based on last time it was closed. This is "by design". But unforuntately there are so many different windowing systems, and musescore is getting that offset info from whatever windowing system it is running on, but sometimes I think the fault is really with those windowing systems.

I don't know of an easy way to solve this problem, exept maybe by having MuseScore.ini always use a default offset of "pos=@Point(0 0)" and then require an explicit command if want to use a different offset (as opposed to current situation where always use previous execution's window position).