Improper window sizing with multi-monitor system

[Edgar]

I downloaded the just-released:
MediaMonkey_2024.0.0.3057_Debug
and tested on my multi-monitor system. The 3-monitor system is set up as (see images* below) :
[1920x1080] [2560x1440]
[1920x1080]
the “ease of access” text setting is 225%.

I am only examining two windows – the main MediaMonkey interface window and the CD ripping window. To the best of my recollection, MediaMonkey_2024.0.0.3043 had serious problems sizing both of these windows (if not that version, MediaMonkey_2024.0.0.3005). Both windows opened way too large to fit on my 3K primary monitor or either of my 2K secondary monitors. Additionally, they were very difficult to resize using a mouse. Neither window remembered its size and location – always opening “way too large” and at a location which made it virtually impossible to drag or resize.

The good news is the main window is now behaving properly**. The bad news is that the CD ripping window has not been improved at all.
**I do not know how to clear out the cache so I am not certain what the behavior will be on a virgin launch.

*Images:

[rusty]

Hi Edgar,

Thanks for the feedback.

I'm able to replicate this, but it was a one-time issue. i.e. I was able to resize the Rip CD dialog so that on subsequent launches it displayed correctly. Did that not occur for you?

In any case, tracking this at https://www.ventismedia.com/mantis/view ... 141#c77108

Thanks!

-Rusty

[Edgar]

The CD ripping window did start remembering its size and location in 3051 or 3053 but, as you point out, it's default location/size is wrong.

Additionally, it seems to sometime forget and revert to the default (wrong) size/location. I think that this is also been improved in 3053 – it only reverts to the default size/location if I install a new build over the previous one (3051 seem to revert randomly). This would be acceptable if the default was usable. Unfortunately the default is not usable (here) because none of the sizing borders are on screen so I may not sized or drag the window. I wrote a small C# utility which allows me to size/position any active window so, for me, this is not insurmountable.

I will not have time to experiment with 3053 until later this week… Results to follow.

[rusty]

Hi Edgar,

fyi, don't spend too much time on this as we've made more fixes to this functionality in build 3058+ which will hopefully become available in the beta forum within the next few days.

Thanks!

-Rusty

[Edgar]

eagerly awaiting…

[rusty]

It was posted last night! Let us know... Thanks!

-Rusty

[Edgar]

I installed 3059 and renamed both AppData folders in an effort to simulate a brand-new launch – it seems to behave like a brand-new launch.

The main window opened maximized on my primary monitor (2560 X 1440; 100% scaling). I clicked the “restore down” button and it restored down with a size which was the same (or slightly larger) as what it was when it was fully maximized. The top left corner was properly located at 0, 0 thus both sizing on the top and left edges was possible. Both the right and bottom edge of the window looked like they were 1 or 2 pixels off the edge of the monitor/taskbar but I did not test to see if I could drag from them. I consider this adequate but would prefer that the default restored down size be slightly smaller and located at 10, 10 so that the window edges were easily approachable with the mouse pointer.

Unfortunately, the CD ripping window sizing is still broken; its top is at 0 but it is considerably taller than my primary monitor. Fortunately, its top is approachable with the mouse pointer and the window can be resized down from there. It does remember this newly resized size and location at the next launch. I consider this usable but not really correct.

[Edgar]

I just downloaded build 3063; I renamed the AppData\Roaming\MediaMonkey5\ folder. This allowed me to simulate a brand-new installation. After installing, things were much worse than they were in 3061 (I did not test 3062 in this manner).

MediaMonkey did open on my primary monitor but, while it was not maximized, its size was much larger than my 3K monitor. It looks like it opened centered on the monitor so it was impossible to grab any of the edges in an effort to resize it. I was able to drag it down and thus reveal the top edge so that I could shrink it down vertically. Even size down to the smallest vertical size, it was still incredibly tall!* I was able to shrink it down horizontally but doing so trashed the text on the welcome screen.

*The minimum possible height is considerably more than 1080 pixels!

Leaving it on my primary monitor, I closed MediaMonkey. I then relaunched it by double clicking on the desktop icon. It successfully restored itself to my primary monitor.

I dragged it to my secondary monitor (1920 X 1080; 100%) – it is considerably too tall to fit. I closed MediaMonkey while it was on my secondary monitor then I started it again – successfully remembered its size and location. I then dragged it to my tertiary monitor (1920 X 1080; 100%) – still too tall to fit – it successfully remembered its size and location.

Next I dragged it back to my primary monitor and maximized it and closed it. I then restarted and it successfully open maximized on my primary monitor.

It seems that the biggest issue is the default initial opening size. I suspect that you have some code** which examines the primary monitor’s resolution and scaling and chooses an appropriate size based on that. It also seems like it probably chooses the GUI fonts size based on that information – BTW, that font is too large. I have found that 80% of the primary monitor’s working area’s both with an height works reasonably well.

**If not, I would be happy to provide something in C# which does an good job of this.

Another major problem is the minimum window height – it is being set way too tall which makes it impossible to resize the window to fit even my large 3K monitor.

[CrashMonkey]

Wanted to say you could Ctrl+scroll to make gui smaller/bigger. But just notices that seems like it ain't working anymore. Used to work in the past.

[Lowlander]

Correct, you can't zoom the interface like that in MediaMonkey 2024. You have options for size in certain Skins and Windows DPI/Text Size settings.

[CrashMonkey]

Are you sure? I have MediaMonkey 2024 with rc1 running on one of my systems, where zoom scroll is still working.

[Lowlander]

Yes, that's an old build.

[CrashMonkey]

So smaller zooming to get more info on screen is removed as functionality? I actually really like that in some cases.

[Lowlander]

It was never intended as a method/feature and caused all kinds of scaling issues.

[Edgar]

IMHO, the default text size and should be small enough to either: work at every resolution/scaling/accessibility setting; be very robust in detecting those settings and choosing a font size which works at the user’s settings. The first will be ugly at lower settings and extremely hard to read at higher settings – while 14 point might initially seem a reasonable “Goldilocks” size, I believe it is well worth the small amount of code necessary to adjust the initial default font size to the user’s settings.

The later method is one I specialize in. I would be happy to offer code and testing – free of charge.