Window Sizing Issues
Hey everyone,
Whenever I maximise Musescore (2.0.2) to work on it and then close it again, it will reopen minimised and not save the maximisation. I have tried to find a way to change this but there does not appear to be a way and I was thinking this was probably a bug.
I'm running Windows 8.
Thanks,
Louis
Comments
Is there anything unusual about how you are starting MuseScore? Using a desktop icon or some other method? As long as you are not using the -F option, it should remember that just fine. Is it remembering other settings - like, say, if you close the Inspector, or change something in Edit / Preferences?
By "minimized" do you mean just "made small"? If so, that confirms that issue #71416: Main window becomes tiny after being maximized does not only happen on Mac OS X.
It doesn't do that here, Windoes 7 (Enterprise, 64bit), If I maximise, close and open MuseScore it is maximised again
Same thing here just noticed:
1. Open MuseScore (score or empty).
2. Maximize window (button or double-click).
3. Close program.
4. Open program.
5. Restore down window.
Expected result: Window restored to size remembered from step 1.
Result: Window restored to maximized size; only manual restoration possible through mouse-dragging, thereby also de-positioning window.
f51dc11 / Win7 64-bit
(by which Ctrl-U has no effect)
That is a different issue, I think. And something we can't do much about, MuseScore only remembers and saves one setting accross sessions.
Different under the hood, then. And odd in that case, to deviate from standard on such a point.
https://github.com/musescore/MuseScore/pull/2752
Fixed in branch master, commit 03453e1a7c
fix #18452, fix #71416, fix #74811: save/restore MainWindow size
Fixed in branch 2.0.4, commit c05ab52040
fix #18452, fix #71416, fix #74811: save/restore MainWindow size for 2.0.4
Fixed in branch 2.0.4, commit 477485c538
Merge pull request #2767 from jeetee/save_restore_MainWindow_2_0_4
fix #18452, fix #71416, fix #74811: save/restore MainWindow size for 2.0.4
Automatically closed -- issue fixed for 2 weeks with no activity.