View Issue Details

Jump to Notes
IDProjectCategoryView StatusDate SubmittedLast Update
0006144MMW v4Main Panel/Toolbars/Menuspublic2009-11-05 18:372009-11-06 17:57
Reporterrusty Assigned To 
PriorityurgentSeveritymajorReproducibilityalways
Status closedResolutionfixed 
Product Version3.1.2 
Target Version3.1.2Fixed in Version3.1.2 
Summary0006144: Columns in filtered views are mixed up
Description1 On a clean installation of MM (i.e. after uninstalling MM, deleting DB & ini file), the default view displays as would be expected. However, when switching to a filter (e.g. General Music):
--> the columns are displayed completely out of order
--> the columns are displayed in an order that doesn't match that of the configuration dialog

2 In addition, the default config for e.g. General Music has custom column orders shown by default. I'm not sure why this is the case--is there an out-of-date default config?

3a Lastly, changing the column order in the config dialog, doesn't work to fix this. e.g. switching Artist and Album, doesn't cause the column order to get mostly fixed--it just reverts Artist an Album, but leaves Genre, Rating, Track#, Path, Bitrate, Track Leveling, Played #, File Size, and Last Played fields in the wrong position.

3b Similarly, changing the order of the columns and/or enabling/disabling columns via tracklist column headers doesn't update the dialog as one would expect (i.e. the two never match).
  
See the attached screenshot.
TagsNo tags attached.
Attached Files
column_sort_order_problem.jpg (207,688 bytes)   
column_sort_order_problem.jpg (207,688 bytes)   
Fixed in build1286

Activities

petr

2009-11-05 22:41

developer   ~0019584

Fixed in 1286

rusty

2009-11-06 07:05

administrator   ~0019594

Last edited: 2009-11-06 16:43

 This is much better in 1286. The only remaining issues are related to installations using an existing database (new databases display as expected):

For existing databases:
1) custom column orders are enabled for most filters and the custom orders are completely strange for some filters (e.g. Title is the 15th field, OR Artist/Album / Album Art is after ~10 fields rather than at the beginning).

2) when custom column orders are enabled, they don't initially match the order of the columns _until_ the user re-orders the columns--at that point a refresh is triggered.

When I tested a clean db from 3.1.1, it exhibited the same problem
==> it's a long-standing issue.

However, there's one new bug:
Upon upgrading from 3.1.1 --> 3.1.2, the configuration changed slightly:
Custom order (for columns) was changed from Checked to Unchecked.

rusty

2009-11-06 17:57

administrator   ~0019605

Petr confirmed that the 'bug' isn't really a bug and that this change from 'custom' in 3.1.1 to custom disabled in 3.1.2 only occurs when the filter hasn't been modified by the user.