View Issue Details

IDProjectCategoryView StatusLast Update
0016804MMW 5Main Panelpublic2022-11-25 00:15
Reporterlowlander Assigned To 
PriorityurgentSeverityminorReproducibilityalways
Status assignedResolutionopen 
Product Version5.0 
Target Version5.2 
Summary0016804: MediaMonkey leaves trace on other monitor when maximized (multi-monitor)
DescriptionIf MediaMonkey is shown on 2 screens (not maximized) and then maximized it leaves a few pixel trace on other monitor (it is correctly maximized though).
Steps To Reproduce1) Open MediaMonkey and have it display partly across 2 monitors
2) Maximize MediaMonkey
3) A few pixels width of MediaMonkey window will be shown on the other monitor

Screen resolutions, DPI and which monitor don't matter
Additional Informationhttps://www.mediamonkey.com/forum/viewtopic.php?f=30&t=96860
TagsNo tags attached.
Attached Files
Fixed in build

Relationships

related to 0018684 closedrusty Multi-monitor: Window can become unresizeable 
related to 0015701 closedrusty Menu issues in multi-monitor environments / windowing problem 
related to 0018847 closedpetr Update Chromium to v98 
related to 0018683 closedpetr Multi-monitor: MediaMonkey always opens on the 'Main display' when maximized 
related to 0018701 assignedpetr Dialogs resize after maximizing / switching between monitors 

Activities

peke

2020-07-15 17:13

developer   ~0058979

Looks like rendered Window borders of MM5 are not correct and are in the offset by 16 pixels.

Attached Images from Screen Capture Apps that have option to capture/focus on single windows only which info gets from OS

As pointed in the past my http://www.happymonkeying.com/forum/MultiMonitor.rar app detects screens independently of OS and can precisely set Window Size and pos (Thus not sure how well it will work after 10 years from making) As from Martin say in ~0058854 it is chromium rendering issue that do not sync OS Window Borders with Rendered Window.

drakinite

2021-01-15 04:42

developer   ~0061363

I think the same rendering bug causes this strange artifact on the Web node. When MM is maximized, it overlaps on the left, bottom and right. But only when it's maximized.
image.png (704,658 bytes)