View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0002125 | MMW v4 | Synchronization | public | 2005-11-01 13:01 | 2005-12-18 07:56 |
| Reporter | rusty | Assigned To | |||
| Priority | urgent | Severity | tweak | Reproducibility | always |
| Status | closed | Resolution | fixed | ||
| Summary | 0002125: 'Copy' functionality is active for MTP devices that don't support copy | ||||
| Description | For MTP devices such as the Creative Zen Touch or Creative Sleek, when I select a track on the device and try to copy/paste it, I receive the following error on the paste operation: Could not find file '\Music\<Artist>-<Title>.mp3', it will not be copied. So the bug is either that: 1) the copy operation _should_ work OR 2) the copy commands should be greyed out if they're not active | ||||
| Tags | No tags attached. | ||||
| Fixed in build | 926 | ||||
|
|
Generally speaking I agree, however I'd rather not spend time on this (doesn't seem to be a big issue) and rather wait for a more complete implementation that would let us do 1), i.e. make file level operation even on tracks uploaded to MTP devices. This could come in 2.6. |
|
|
Are you sure that 1) is possible? i.e. when I try to copy files from the device to a drive directory via Windows Explorer, that doesn't work either (i.e. COPY is disabled). If, such operations are in fact impossible, then shouldn't we just grey out 'copy' for such nodes? |
|
|
1) Isn't directly possible, the tracks on MTP devices aren't part of filesystem. However, it could be implemented so that WMDM functions would be used for downloading tracks back from device and it would allow implementation of functions like: Copy, Edit properties or even Play. |
|
|
As discussed with Jiri, the problem is that this issue is perceived as a blatant bug. I would suggest that we take whatever action is most expedient to resolving this. i.e. if, in the short term, it's too much work to use the wmdm driver for such actions, then it might be worthwhile to just extend the framework to show which actions are available vs which are disabled. Leaving this open in the hope that it can be resolved during the late beta period (since there are no UI changes). |
|
|
Fixed in build 926. - This was fixed and also some other minor related issues were resolved (AVs in some special cases of popup menus). |
|
|
Verified 926. |
