View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0003013 | MMW v4 | Properties/Auto-Tools | public | 2007-04-20 09:49 | 2007-04-24 21:54 |
Reporter | Ludek | Assigned To | |||
Priority | urgent | Severity | minor | Reproducibility | always |
Status | resolved | Resolution | fixed | ||
Product Version | 2.5.5 | ||||
Fixed in Version | 3.0 | ||||
Summary | 0003013: Linked covers are cleared sometimes by editing track properties. | ||||
Description | I found a bug that is presented in both MM 2.5 and MM 3.0. If you edit track properties and your active page is the page with cover list and there is some linked covers presented (saved as a file) and you have '[x] Apply to all tracks on the album' checkbox choosen and then you click the next button on the page in order to view properties of the next song then the linked covers are cleared. Note: the next song has to be of the same album I found out that this occurs since the song is in tagging queue because of the previous song is in saving process and had the '[x] Apply to all tracks on the album' selected. | ||||
Additional Information | This is most probably related with http://www.mediamonkey.com/forum/viewtopic.php?t=17138 | ||||
Tags | No tags attached. | ||||
Fixed in build | 1030 | ||||
|
I'd say that a proper fix to 0002609 would fix this issue, because each track would have only one TSongListData structure in memory, i.e. it wouldn't happen that each structure of one track has different data. Agreed? However, I don't think this issue is related to http://www.mediamonkey.com/forum/viewtopic.php?t=17138 , I thought that it was resolved by something in FormSongProperties dialog, wasn't it? |
|
1. No, the problem is in SaveCoversForAlbumId() -> SaveCoversForList() where only covers with CoverStorage = csTag are added. Is there any reason for it? If all covers are added (that should be in my opinion) then this bug is fixed! 2. Re: http://www.mediamonkey.com/forum/viewtopic.php?t=17138 Yes, the first bug (Posted: Tue Apr 17) was resolved by 0003008 , but I meant the second (Posted: Wed Apr 18) |
|
Fixed in build 1030. |