View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0002359 | MMW v4 | Synchronization | public | 2006-02-10 03:24 | 2006-02-10 19:02 |
| Reporter | rusty | Assigned To | |||
| Priority | immediate | Severity | major | Reproducibility | always |
| Status | closed | Resolution | fixed | ||
| Summary | 0002359: Tracks are deleted even when outside the synch path | ||||
| Description | In build 943, if the user has configured MM to delete tracks that aren't in the synch list, then the tracks are deleted/proposed for deletion even when they are outside the Synchronization path. e.g. If tracks are synched to \Music and \Playlists, then the user is given the option of deleting: a) tracks that are not Audio files or Playlists b) tracks that are outside \Music and \Playists I'm fairly certain that this wasn't the case in previous builds. | ||||
| Tags | No tags attached. | ||||
| Fixed in build | 944 | ||||
|
|
This has always been this way, user can use the field for Exceptions in order to ignore some folders/files. |
|
|
I'm pretty sure that the behaviour in the current build is different. When I do my test synching, I almost never use 'Exceptions', and in this build I was prompted to delete the following, and this never occured in previous builds: IFP880: Synched to /Music/<Artist>/<Album>/<Title> Was prompted to delete: /VOICE/VOICE001.REC /VOICE/VOICE002.REC /VOICE/VOICE003.REC etc. On the Creative Vision, with the same synch mask, I was prompted to deleted the following: DeviceInfo.xml DevIcon.fil DevLogo.fil WMPInfo.xml \Video\Extremefidelity.avi \Video\xxx.avi On the PMC-120 and H10, with the same synch mask, I was promted to delete anything, so I'm not sure why this occurred with the above 2 cases but not with the latter 2 devices. Note: as far as I can remember, in the past, MM only deleted: a) supported file types b) from the directories to which it synchs (e.g. it would never delete from /Video ) |
|
|
Fixed in build 944. - This is caused by the fact that for some devices MM knows what formats they support (either because we have a specific plug-in, or because the device reports it using WMDM). a) This wasn't ever implemented, but I added it in build 944. It makes sense to handle only files MM understands (in addition there's still also the test for the extensions device supports). b) This wasn't ever implemented, although it was discussed. It would have some disadvantages and since a) is fixed there's also a little need for this. |
|
|
Verified 944. |
