Album&Tracks view mode misbehaving

Report bugs & feature requests for MediaMonkey 5 and learn about the newest builds.

Moderator: Gurus

Barry4679
Posts: 763
Joined: Fri Sep 11, 2009 8:07 am
Location: Australia
Contact:

Album&Tracks view mode misbehaving

Post by Barry4679 » Fri May 10, 2019 1:16 am

https://www.dropbox.com/s/xby6867gny665 ... s.png?dl=0

Steps
* Add|Rescan some tracks from a new location
* navigate via EntireLibrary|Location
* drill down to these new tracks
* set view mode to Albums&Tracks, set Show All Album Tracks control to collapsed setting

#1 (as marked in attached diagram) .... album art column width defaults to very tiny, causing incomplete horizontal strip from Summary row to be displayed ... only enough vertical space for just 1 track

The small art column width exposes some other unhelpful UI quirks.

#2 (same diagram) ... click "Show All 25 tracks" button .... just a subset of tracks are displayed ... no indication, nor a reminder, that this is just a subset .. no way to scroll down to the remainder of tracks, which is confusing because I just clicked "show all album tracks" ... my PC has two screens ... if I move the cursor to the other screen, after a small delay MM5 auto-switches to show all tracks for the album

#3 (same diagram) ... some album art behaves differently when manually reducing the column width for album art ... the column width can be reduced smaller than the album art is able to, which causes the column headings to become misaligned ... and something screwy happens to the Summary column, ie. data duplicated

PetrCBR
Posts: 1631
Joined: Tue Mar 07, 2006 5:31 pm
Location: Czech
Contact:

Re: Album&Tracks view mode misbehaving

Post by PetrCBR » Fri May 10, 2019 3:43 am

Thanks. Will check.

Barry4679
Posts: 763
Joined: Fri Sep 11, 2009 8:07 am
Location: Australia
Contact:

Re: Album&Tracks view mode misbehaving

Post by Barry4679 » Sun May 12, 2019 3:48 am

Retested with version 2175 published today.

Issues persist.

I noticed that the display issues seem to be specific to when navigating via the node>Location>xxx route, as described in the steps in my earlier post.

Post Reply