1345: Bugs with Show Art/Show Details [#7499]

[carloscs]

Steps to reproduce the bugs:

1. Start playing some music.

2. Tab 1: In the Library tree select the Music->Album node and now choose View -> Show Art
-- album images appears -> OK.

3. Open tab 2: select one album and choose View -> Show Details
-- album details appears -> OK

BUGS:
-- when a playing track changes a lot of detail entries filled with "Node" appear under the existing album tracks
-- go to tab 1 -> in the library tree select one album -> album details are shown instead of the album art.
-- Doing the reverse also works badly: in tab 1 select View->Show Art and in tab 2 now the album art appears instead of the album details.

Win7x64

[Lowlander]

Can you post a screenshot of this node effect?

One issue I noticed is that if you change the View in one tab, this view is now set for all tabs when you refresh or change node. This is probably due to the View setting being saved for the Collection and each time you load a node it checks what the View setting is for the Collection.

[carloscs]

One issue I noticed is that if you change the View in one tab, this view is now set for all tabs...

I almost asked if the view being applied to all tabs was a bug or a feature. Seems like my brain was afraid of wasting bits by asking the question

Can you post a screenshot of this node effect?

Seems like I can't reproduce it today. Friday I didn't have any trouble making it happen

FWIW, here is a more detailed description of what happened:

In the second tab with the view changed (afair) to "Show details", the normal tracks of the album chosen in the library tree where shown. As soon as the playing track changed, a lot of rows (very possible about 800, the number of albums I have in MM) appeared, with all the columns (in the new rows) having the "None" content. The rows actually existing in the album where unchanged.

If I manage to reproduce the bug I'll post again...

[PetrCBR]

It's intended behavior. When you change a view mode in one tab, other tabs will not change view mode until you'll change collection in them, because each tab settings is unique for the instance.
For example:
- you have open 2 tabs with music collection selected
- change view mode in first tab (this mode is now a default for the collection)
--> it will not change view mode in second tab !
- switch to second tab (this tab still have 'old' view mode)
- move to another collection and then back to music
--> new view mode (changed in first tab) will apply as this view mode is now a collection default

[Lowlander]

I observe the following
- Open 2 tabs in Music Collection
- Change view in tab 1
- Change to tab 2
- Refresh or click any node in Music Collection
View is also updated to the one used in tab 1

and

- Select Music Collection in tab 1
- Open tab 2 by right click on Music node > Open in new Tab(don't select it)
- Change view in tab 1
- Switch to tab 2
View in tab 2 is also updated to the one used in tab 1

I think ideally the changes in view should not propagate to other open tabs as this gives more usability to the tabs. Understandably the last set view is the saved view and will be used for new tabs or after restart of MediaMonkey (although it could also be the view of the last open tab).

[carloscs]

I think ideally the changes in view should not propagate to other open tabs as this gives more usability to the tabs.

That's my expectation too. Each tab should have it's own independent view. Tabs are still useful with only one common view, but this greatly reduces the potential usability of the tab experience.

Understandably the last set view is the saved view and will be used for new tabs or after restart of MediaMonkey

Aren't tabs preserved between restarts ? They should be, have to try this.

[Lowlander]

Yes tabs are preserved. It's meant to define what View should be saved as the new View.