Editor windows open on secondary monitor even when it's disconnected
Type
Graphical (UI)
Severity
S4 - Minor
Status
closed
Regression
No
Workaround
Yes
Project
When a secondary monitor is used to edit scores, the score window will open in the same area when MuseScore is restarted with the second monitor disconnected. As a result the score edit windows will be invisible.
The only remedy is to reconnect the second monitor.
This is an awkward bug: since my main computer is a laptop the secondary monitor is absent when I'm away from home and I can't edit any scores until I get back.
This can be worked around by repositioning the windows to the main monitor before quitting MuseScore, but that can only be done when the secondary monitor is still connected, not afterwards.
Comments
Confirmed.
Version: 1.1
Revision: 4611
Mac OS X: 10.5.8
Disconnecting the second display *while running musescore* correctly gathers the windows.
"Disconnecting the second display *while running musescore* correctly gathers the windows."
That is hardly a solution: when the second monitor is still connected, I can also gather the windows manually.
The problem occurs when I'm away from home (and the second monitor), this happened to me again recently when I forgot to reposition the windows before quitting MS. In that situation you're effectively locked out of the application until you connect a secondary display and if none are available there is simply nothing you can do.
A "gather windows" command would be very helpful in this situation, and shouldn't be too hard to implement.
"That is hardly a solution..."
Sorry. Not implying this is in any way a solution. Just confirming that it affects me too. The problem drove me crazy for half an hour while I tried to get the window while away from my second display too! I could see it with Expose and Space, could drag it from space to space, but could never drag it to the principle display. The only potential solutions I found were 1) Use an Applescript to move all windows back to the main desktop, or 2) Delete the preference .plist file. (As I have a second monitor, I ended up plugging it back in.)
Some people recommended that Window -> Zoom can help, but as musescore does not have a Window menu,
I was just emphasizing that this is an issue with how the placement information is saved, not with the window placement in general. Hopefully this helps isolate the issue.
Well, Nice to know I'm not the only one having this problem.
That applescript solution sounds like it might be very useful. Could you share it here?
I have not tried this, but a google search for "applescript gather windows" reveals several options.
http://hints.macworld.com/article.php?story=2007102012424539
http://www.jonathanlaliberte.com/2007/10/19/move-all-windows-to-your-ma…
http://forums.macrumors.com/showthread.php?t=359732
This seems to be a common issue on macOS, not just with MuseScore. I found the following page with a host of workarounds.
https://www.technipages.com/macos-bring-window-back-onto-screen
Can someone confirm if this is still an issue on a current (10.12) macOS on MuseScore 3.6.2?
If this is still an issue, I am leaning towards setting this to a “won’t fix”.
Happens on Windows too.
My original issue was that the windows that are placed on the second monitor become inaccessible when you start Musescore without that second monitor connected (i.e. when away from the location where that second monitor is).
That issue seems to have been fixed, on OS: macOS 10.16, Arch.: x86_64, MuseScore version (64-bit): 3.6.2.548020600, revision: 3224f34
The window now opens (correctly) on the primary monitor (the only one available).
I would regard this issue as FIXED (well done!)
Note: due to the time elapsed since my original issue I can no longer test this on the same hardware as where I had the issue originally.
Probably something the newer Qt version used by newer MuseScore versions did fur us
> I would regard this issue as FIXED (well done!)
> Note: due to the time elapsed since my original issue I can no longer test this on the same hardware as where I had the issue originally.
No problem, as long as it is fixed in latest MuseScore, current-ish version of macOS. Thousands more old issues to go through, that may have been fixed since ...
Automatically closed -- issue fixed for 2 weeks with no activity.