View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0004136 | MMW v4 | Properties/Auto-Tools | public | 2007-12-12 20:45 | 2007-12-16 21:42 |
| Reporter | rusty | Assigned To | |||
| Priority | immediate | Severity | major | Reproducibility | always |
| Status | closed | Resolution | fixed | ||
| Product Version | 3.0 | ||||
| Summary | 0004136: Changing properties in My Computer doesn't update the DB | ||||
| Description | As reported by a user at: http://www.mediamonkey.com/forum/viewtopic.php?t=22866 when changing Track properties in the My Computer node, MM doesn't update the DB if the Track happens to be in the DB. | ||||
| Tags | No tags attached. | ||||
| Fixed in build | |||||
|
|
Possibly a regression related to 0002165 ?? |
|
|
I'm not sure this can be considered a bug, because: As discussed in 0002165, My Computer node should show content of tags and nothing else (neither data inferred from filenames nor data from Library, there's a Location node for this purpose). However, if we take this as a fact, then I don't think changes in My Computer node should automatically update Library (unless there's File Monitor running). If for no other reason, then at least because user can overwrite values that he/she doesn't even see. E.g. if track A has title 'Title 1' in Library and title 'Title 2' in tag (well this shouldn't happen, but it definitely can), changing 'Title 2' string would completely overwrite all different values in Library. So, my summary is, if user wants changes in My Computer node to be reflected in Library then either: 1. Use Location node instead. 2. Use File Monitor. 3. Rescan Library after making the changes. |
|
|
Agreed. |
|
|
Something very strange is happening. In build 1118, it seems that edits in the My Computer node ARE triggering changes in the DB. As I explained earlier, I don't think that this is such a bad thing, though I tend to agree with your point of view. What is more worrisome, is why would there be a change between build 1116 and build 1118? I thought nothing changed here? |
|
|
Actually, I was wrong in my original description, as far as I can see, the issue described in this bug actually never existed. There wasn't any change in recent builds in this area, how it have worked could be described as: 1. My Computer node shows track values as they are stored in tags, DB isn't taken into account. 2. However, if user starts editing (either in Properties dialog or in-place) properties of a particular track are read from DB and shown, so that when user confirms the changes, track is properly updated (both tags and DB) and the issues described in my previous post here can't occur (e.g. overwriting values that user haven't had any chance to see). Question is which behaviour is better. For the short term (i.e. 3.0 release) I'd rather leave it as is, it _works_ and doesn't seem to cause any big problems. For longer term (i.e. some of the next versions) I'd probably prefer the approach I originally described, i.e. that DB won't be used at all in My Computer node. |
|
|
Closing as it seems there was on issue, at least as far as this release is concerned. |
