getmusicbee.com

Support => Questions => Topic started by: scatterkeir on August 18, 2019, 12:26:46 PM

Title: Multi-monitor: Window management problem, worse with 3.3 Update 1
Post by: scatterkeir on August 18, 2019, 12:26:46 PM
On my two monitor setup (on Windows 10) I've had a minor issue for a while where sometimes a thin strip of the right-hand edge of MusicBee (I generally run MusicBee fullscreen on the left monitor) appears on the left-hand side of the right monitor. It wasn't simply the window being too big for the monitor, as it looked like the strip was at least partly a duplication of what was correctly appearing on the right edge of the left monitor).

I've just installed 3.3 Update 1 (I was previously on 3.3) a few minutes ago and it looks like that issue might have improved, but I now have a more annoying issue where if MusicBee is the active window any click on anything else will do nothing, I have to alt-tab to another application after which it's fine.

I use the skin Bee78, is the another skin I should use to rule out it being a skin-specific issue?
Title: Re: Multi-monitor: Window management problem, worse with 3.3 Update 1
Post by: Steven on August 18, 2019, 03:07:19 PM
I cant think of anything that has changed between v3.3 and v3.3 update 1 in terms of screen management.
I dont have a multi-screen setup to test this but i cant reproduce on a single screen and no one else has reported this issue, so I dont think i can help
Title: Re: Multi-monitor: Window management problem, worse with 3.3 Update 1
Post by: scatterkeir on August 18, 2019, 03:27:38 PM
Thanks for your swift response, Steven. Perhaps someone else will have an idea.

I should probably also say that I'm on Windows 10 18362.295.
Title: Re: Multi-monitor: Window management problem, worse with 3.3 Update 1
Post by: scatterkeir on August 18, 2019, 03:42:48 PM
Good news - acting on a hunch, I seem to have fixed it with a reboot.

I'm guessing that just restarting explorer.exe would have worked as well.

Perhaps it was a factor that the instance of explorer was running since before I updated, but I imagine that the root cause was simply Windows 10's window management's occasional flakiness.