This is great and on my WXP works very well! Thank you!
But, I use a lot of extra database fields for classical music (composer, orchestra, conductor, movement, soloists etc.) and other database fields for images (specifically for artworks like galleries, paintstyle etc.). And I also don't use quite a number of fields such as ratings etc.
But, when I select properties I see them all and that's a lot! I would like the sticky view extended to the properties panel. When I hide fields in the view panel, they should also hide in the properties panel.
And also the sorting order should be taken over to the properties panel.
My general properties now look like this (too many non related fields and badly sorted!):
Album (used for collections in artwork)
Artist (used for music artist, but also for painters)
Choir (classical music)
Comment
Composer (classical music)
Conductor (classical music)
Gallery (artwork)
Genre (genre in music and images or artwork have totally different meanings)
Movement (use this field right now for classical music and for artwork, which is not ideal)
Name
Opus (classical music)
Orchestra (classical music)
PaintStyle (artwork)
Ratings (not used)
Soloist (classical music)
Track # (music only)
Year (different meaning in music and artwork)
I would prefer to see only those fields related to classical music in the proper sort order and only those fields related to artworks when selecting the artworks group.
Probably the best way to define which fields to see would bee when creating a new View Scheme Group in Media Library. I would create a new View Scheme Group "Artwork" displaying only the fields Artist, Name, Gallery, Movement, Genre, PaintStyle
Also: The drop down lists in the properties fields should display only the values according to the selected media type (or even better according to the selected View Scheme group). If I have to select an artist in the music world, I don't want to see painters such as Picasso, Monet, Cézanne, Renoir etc. and vice versa.
I feel the "New View Scheme Group" in Media Library could be used more extensively to properly define how you want your database views set up properly.