|
|
You don't need to restart for this to occur.
1) Go to Playlist
2) Enable Column Browser
3) Change to 2 Columns
4) Go to Playlist without Column Browser
5) Go back to Playlist with Column Browser
6) 3 Columns are shown
Also
1) Go to Collection node (tested with Artist in Artist and Details node)
2) Enable Column Browser
3) Go to Playlist node without Column Browser
4) Go back to Artist node and Column Browser is missing |
|
|
|
Fixed in 1395 |
|
|
stephen_platt
2011-06-23 02:57
developer
~0026302
|
verified 1395 |
|
|
|
Not fixed here on 1395.
Issues seen:
- Not removing columns when selecting Remove Column
- Not remembering 2 column setting returning to 3
- Showing 2 columns, but 3 column headers |
|
|
|
fyi, works for me as well. |
|
|
|
Martin, I'm resolving this. If you can still repro the bug, please re-open with details. |
|
|
|
Are you saying the log shows no clues on what is happening?
1) Still occuring when removing any column other than the last column. Removing 2 columns on a 4 columns setup will result in 4 columns with the last columns field as field.
2) Changing columns seems to be remembered sometimes (working mostly in Playlist node). In the Music Collection there seems to be no issue remembering the column layout, but in Playlists this isn't working.
3) When going to 2 columns it will show 3 phantom column header as in screenshot. And it will show it in all nodes even those that showed 2 columns correctly (after restart 2 columns is shown correctly).
Second log added (debug2.zip)
|
|
|
|
I can confirm that all three issues exist.
1) When there are four columns, removing a column other than the fourth column fails.
2) Non-collection nodes (Playlist, Search, My Computer) don't persist column browser settings. Should probably be tracked as a separate bug.
3) Various artifacts show up in the column browser headers (sometimes at startup, but most commonly when adding/removing columns).
See video here: http://screencast.com/t/en6PHSdx45d |
|
|
|
Fixed in 1396 |
|
|
|
Unfortunately 1396 behaves exactly the same as 1395. |
|
|
|
I was set wrong build number. It should be in 1397. |
|
|
|
Verified in 1397. |
|
