[quote=drakinite post_id=475880 time=1608506677 user_id=107828]
Do you see it on Discord? [..]
[/quote]
Yeah, it has been a known issue with [url=https://www.reddit.com/r/discordapp/comments/4xfc9y/when_maximizing_discord_on_one_monitor_you_can/]discord[/url] [url=https://www.reddit.com/r/Windows10/comments/i90l92/full_screen_app_on_one_monitor_leaks_into_the/]for[/url] [url=https://linustechtips.com/topic/967856-discord-leaks-over-to-my-other-monitor/]a[/url] [url=https://support.discord.com/hc/en-us/community/posts/360071530292-Discord-overlap-on-multi-monitor-]while[/url] that still happens in its current version of the desktop app.

Sorry I don't use Discord so can't confirm that one.

Do you see it on Discord? I haven't used the Discord desktop app in a while (after switching to the browser version in Rambox), but I used to see a 1-2px border on there. Not as bad as MM5 though.

Not just me then! Renaming persistent.json doesn't make any difference here, same issue happens. Seems strange that it only affects MM5. All other windows from system to 3rd party apps (including Chrome) display fine when maximised apart from MM5. Not a big deal but now I can't unsee it!

Hi there,

This is a known issue; I've detailed it here in the past: https://www.mediamonkey.com/forum/viewtopic.php?f=30&t=96860
It's tracked as: https://www.ventismedia.com/mantis/view.php?id=16804

I agree that it's strange and annoying, but hopefully it can be resolved for 5.0.1 :crossed_fingers: :slight_smile:

Edit: When I renamed persistent.json and reopened it, the black overlap initially didn't show up; but if I closed and reopened MM once more, the black overlap showed up again for me.

I'm unable to reproduce on a dual monitor with 2288.

Try renaming persistant.json: https://www.mediamonkey.com/support/knowledge-base/mediamonkey-install-config/error-message-on-startup-error-during-player-initialization-reset-mediamonkey-interface/ while MediaMonkey is closed and then see if the problem persists when you start MediaMonkey again.

I'm running latest MM5 (5.0.0.2288) and Windows is set at default native resolution for all 3 monitors (1920x1080) all at default DPI scaling and text size. Every other app or window works as expected when maximised (including MM4) and MM5 is the only one to exhibit this display issue that overlaps onto the adjacent monitor when maximised.

Which build of MediaMonkey and do you have a non-default DPI or Text Size setting in the Windows settings?

Bit of an odd one but this bug only happens with MM5 out of all the apps on my Win 10 system. I have a 3 screen setup and usually put MM5 on my leftmost monitor. If I click the [maximise] button at top right of MM5 I can see a very small portion of the program's window overlapped onto my 2nd (center) monitor.

Here's a screenshot where you can just see the border of the program window.

[url=https://ibb.co/RN9sLdJ][img]https://i.ibb.co/VxtzX5k/charset-Invalid-Charset-Id-binary-comment.jpg[/img][/url]

The same thing happens if I put MM5 on my 2nd (center) monitor and click [maximise] - I can then see a small portion of the window on my 3rd (right) monitor. It should be maximised only on whatever screen it's running on, but for some reason a portion of the window 'bleeds' onto the adjacent screen.

I've tried this with a bunch of other apps (GIMP, Win Explorer, Chrome etc) and MM5 is the only one that does it.

Also, if I then click the focus onto a different program, the overlapped part of the window on the adjacent monitor disappears. But if I click back onto MM5 the frame is visible again. MM5 is definitely running full screen maximised when this happens.

I'm sure it's possible to rectify it somehow, though, even if it is - Namely because Slack and Discord only extend a couple pixels at max, and it's not that bad. Maybe through the arguments/flags that Chromium takes when it's launched? Is that something that I'd be able to mess around with in my install files, as with all the frontend javascript? Or is the code that launches the initial Chromium window(s) compiled into an .exe?


I don't really mind if it takes a long time to fix, because there's half a million things on your guys' plate for MM5. But I'm happy that you listened to me and added it to the tracked issues. :heart: :slight_smile:

Then it maybe the underlying Chromium that has a bug, not MediaMonkey.

Wow, that's... weird. Huh.
Well, maybe whatever fixes the UI remnants can also fix the black bars for me. It's weird, but it seems like this extending-into-other-displays problem is common with native apps that use Chromium. Discord and Slack have that issue— However, it's slightly different, because in their case the window itself is spread out larger than the display. (In Discord's case, I often see the unread markers on the left side of the screen cut off)

No black bars here, just a remnant of the window from before maximize.

If you have another program open on your second monitor (For example, a web browser), and then maximize MediaMonkey on the first monitor, there should be a black line extending into the second monitor, displaying over the other program. At least that's what I've been experiencing, and that's what the original post was about.

I did notice that sometimes bits of the UI showed up over that black line, but I didn't realize it was due to the window extending across both displays. I figured it wasn't worth including, because if the black bars were fixed, then the associated UI remnants would also be fixed. Sorry if I was unclear.

I have a black desktop, so yes, that is what I see and reported, but this does seem different from what you originally reported. Because in this scenario the window is maximized on single monitor, but remants of window remain on other monitor. Whereas it seems you see the window extend on 2 monitors after maximizing.