2135: display problems

[Barry4679]

Changing skins, with the Player panel toggled off, causes "Bottom Panel" to be also toggled off in Tools|Options|Library|Layout ... which means that you can longer toggle the player panel on|off with the View menu or with Ctrl+Alt+L

Also go to Tools|Options|Library|Layout and Set Bottom panel on, but leave Player toggled off ... press OK ... the change is not persisted

Also Toggle the player on|off a few times via Ctrl+Alt+L ... after a few iterations the Auto-Tag panel is displayed (?) ... close it via Cancel ... you can no longer display the player panel, ie. "Bottom Panel" has toggled itself off.

When I first started 2135 (clean install, after deleting prior MM5 installation) ... there was no footer line at the bottom of List view (ie. # files, # GB, # hours etc) ... the only way that could restore this was toggling back and forward to|from a different skin. ... After testing for a while the same thing happened to the footer. ... I use either of the two material design skins.

Their is an alignment problem when the Bottom (Player) panel is not displayed and the window is maximised.
https://www.dropbox.com/s/9bo3rgl2201xv ... t.png?dl=0

[PetrCBR]

Thanks for a feedback. Player visibility tracked as 15234.

Also Toggle the player on|off a few times via Ctrl+Alt+L ... after a few iterations the Auto-Tag panel is displayed (?) ... close it via Cancel ... you can no longer display the player panel, ie. "Bottom Panel" has toggled itself off.

Auto-tag have Ctrl+L hotkey ... isn't is possible you released Alt key so Auto-tag showed up ?

[Barry4679]

Auto-tag have Ctrl+L hotkey ... isn't is possible you released Alt key so Auto-tag showed up ?

I did do it twice, but I you are probably correct re the "unexpected" auto-tag panel.

But what does happen is that repeated toggles causes the "bottom panel" to become set off in the config.

[PetrCBR]

It is set off automatically when it does not contain any visible panel, but problem was it doesn't changed to visible when any panel visibility changed. I've fixed that.

[Barry4679]

restore screen from maximise also broken.

I opened tabs when MM5 window dimensions were customised
When I toggled MM% to maximise its window, the extra real estate in the panels were not populated.
https://www.dropbox.com/s/yhml0lj926xls ... n.png?dl=0

When I navigate to a new node the middle panel is popultaed correctly, but the media tree remains truncated

[PetrCBR]

I cannot reproduce with current sources. Please, retest in next build.

[Barry4679]

I can't make it happen again now either. ... when it did happen it wouldn't go away. ... looked like the queue handling resize events go blocked somehow.

there is another potential display issue. The Extension dbox shouldn't have Windows to minimise|maximise etc.
https://www.dropbox.com/s/0bgrp280c1xkg ... x.png?dl=0

The Extensions dbox is a modal child window. If someone needs some clear window space and minimises it, it can become confusing. ... eg. I just opened MM5 on one of my screens, dragged it to another screen, and then opened the Extensions dbox, and then minimised it. ... The dbox flys away and hides a tiny stub on the 1st screen, and MM acts disabled and frozen on the 2nd screen. .. It is not reactivated by a single click on MM5 in the task bar. (Windows 10)