You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Windows 10 22H2.
NVidia GeForce GTX 1660 - latest "studio" driver
Dual monitor. But sometimes I use it in single monitor mode if I am using a laptop with the other monitor.
Windows is set to turn the monitors off after a few minutes of inactivity. The computer itself is set to stay on all the time (no sleep, no hibernate, etc.).
I noticed this issue on all Shotcut builds using QT6. Currently using 24.02.29.
There's some combination of having the monitors go into power-saving mode and virtual desktops. I haven't been able to find the necessary ingredients or the exact sequence to reproduce this issue on command. But it seems to happen quite frequently. Typically, it's waiting for an export to run. I may leave the computer while an export is running, then come back at a later time. It's long enough that the monitor(s) powers off per the Windows power management setting.
When you jiggle the mouse to wake the monitors, the graphics of the Shotcut window are a little offset. The mouse interactions with the Shotcut GUI are not registering in the correct place. The work-around is to restore-down the Shotcut window, then maximize it again. Then the mouse and GUI are tracking together correctly.
See attached video.
QT6.GUI.issue.mp4
The text was updated successfully, but these errors were encountered:
Windows 10 22H2.
NVidia GeForce GTX 1660 - latest "studio" driver
Dual monitor. But sometimes I use it in single monitor mode if I am using a laptop with the other monitor.
Windows is set to turn the monitors off after a few minutes of inactivity. The computer itself is set to stay on all the time (no sleep, no hibernate, etc.).
I noticed this issue on all Shotcut builds using QT6. Currently using 24.02.29.
There's some combination of having the monitors go into power-saving mode and virtual desktops. I haven't been able to find the necessary ingredients or the exact sequence to reproduce this issue on command. But it seems to happen quite frequently. Typically, it's waiting for an export to run. I may leave the computer while an export is running, then come back at a later time. It's long enough that the monitor(s) powers off per the Windows power management setting.
When you jiggle the mouse to wake the monitors, the graphics of the Shotcut window are a little offset. The mouse interactions with the Shotcut GUI are not registering in the correct place. The work-around is to restore-down the Shotcut window, then maximize it again. Then the mouse and GUI are tracking together correctly.
See attached video.
QT6.GUI.issue.mp4
The text was updated successfully, but these errors were encountered: