Mouse tracking error upon waking from Windows Power Management sleep
This is a strange one. When I'm working on a score, have MuseScore 4 open on one of my two displays, step away for a bit to the point where my system goes to sleep, come back and wake things up, then MuseScore seems to track the mouse noticeably below the pointer as displayed on the screen. At first I thought MuseScore had stopped responding to the mouse, but eventually noticed the shift in mouse tracking. This happens whether the window is maximized or not.
This does not occur with any other apps running at the time (i.e. does not seem to be an inherent issue with my Windows system upon wake-up).
Doing anything to resize the window (minimize/restore, maximize/restore, etc) resolves the issue (until the next time the system sleeps).
====================================
OS: Windows 11 Home Version 10.0.22621, Arch.: x86_64, MuseScore version (64-bit): 4.0.2-230651553, revision: dbe7c6d
Comments
Are both displays identical? Same screen size? Same resolution?
Does the mouse "wake up" on a different display from "sleep"?
In reply to Are both displays identical?… by Jm6stringer
In my particular case they are not identical, one is a 4x3 format Samsung, the other a 19x6 Samsung, both with different pixel resolutions.
And, I have to apologize for using loose terminology. The computer is set to never sleep, but the power to the displays turns off after a set time so it's the screen coming back on. One of the displays powers up before the other and in that brief time it seems Windows thinks there is only a single display and shows the mouse and all windows on it. When the other display comes back, the mouse and windows revert to proper positions.
After playing some more, it seems that any MuseScore windows that are actually open are fine, it is the ones that had been minimized that, when restored, display this symptom. I notice when first restoring them that they seem to jump a bit on that restore -- likely by the same amount that the mouse tracking is then off by.
If I had to guess, I'd say there must be some weird order to various Windows messages due to the power management stuff and this ends up affecting MuseScore. It's a slight annoyance, nothing more, and since I know it happens it's easily worked around.
In reply to In my particular case they… by thomaswb
You wrote:
After playing some more...it is the ones that had been minimized that, when restored, display this symptom.
Also:
One of the displays powers up before the other and in that brief time it seems Windows thinks there is only a single display and shows the mouse and all windows on it.
It's a slight annoyance...
Depending on the level of annoyance...
Things to try:
Switch cable connections from the monitors to the computer's video interface.
In Windows: Go to Display settings and re-arrange the order of the 2 monitors.
Not strange at all, FWIW, my older copy of Sibelius does not work correctly after wake up, either. And I think some other program that I have. I have set all my systems to never go to sleep. I know Windows 11 doesn't like it. If I'm not going to use my computer for a while. I turn it off.
In reply to Not strange at all, FWIW, my… by bobjp
I have to apologize for using loose terminology. The computer is set to never sleep, but the power to the displays turns off after a set time so it's the screens coming back on. One of the displays powers up before the other and in that brief time it seems Windows thinks there is only a single display and shows the mouse and all windows on it. When the other display comes back, the mouse and windows revert to proper positions.
After playing some more, it seems that any MuseScore windows that are actually open are fine, it is the ones that had been minimized that, when restored, display this symptom. I notice when first restoring them that they seem to jump a bit on that restore -- likely by the same amount that the mouse tracking is then off by.
If I had to guess, I'd say there must be some weird order to various Windows messages due to the power management stuff and this ends up affecting MuseScore. It's a slight annoyance, nothing more, and since I know it happens it's easily worked around.