View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0001587 | MMW v4 | Synchronization | public | 2004-11-11 05:59 | 2004-11-11 14:08 |
| Reporter | rusty | Assigned To | |||
| Priority | immediate | Severity | major | Reproducibility | always |
| Status | closed | Resolution | no change required | ||
| Summary | 0001587: iRiver plugin : user should have a means of choosing the drive letter (in case USB ID is missing) | ||||
| Description | I started writing some text re how to configured H-1xx devices: "The Portable device plugin for iRiver H-xxx devices has been tested only with the H-320, but should work with any H-xxx device. iRiver will be providing us with information that will allow other H-xxx devices to be automatically recognized and configured, but until then.... " HOWEVER, the further I got, the more I realized that we are taking an incorrect approach. i.e. if we don't know the USB Device Identifier, that _SHOULD_NOT_ prevent a user from using an iRiver device with the iRiver plugin. i.e. the user should be able to configure MM to synchronize to the drive letter that is the iRiver device. This is a strategic issue as well--if new devices are released, users should be able to use them without us having to release a new plugin each time. Is there anything that we can do so that users can exercise the H-320 plugin on other iRiver devices (even in the event that we don't get device identifiers)? | ||||
| Tags | No tags attached. | ||||
| Fixed in build | |||||
|
|
I don't think that this is necessary, actually I think it's better to have control over what devices can be used with a particular plug-in, this way we can be sure what they do with a particular device, etc. It isn't problem to release a new version of plug-in on our website. Also, I think that the current version detects H1xx devices because I took 3 USB IDs from an utility distributed with H3xx, my guess is that these IDs are reserved for H1xx, H2xx and H3xx series, but I'm not sure. I would just like to be sure in order to properly configure some other things (e.g. if H1xx doesn't support Unicode then create an older DB version there). |
|
|
Closing. Hopefully it won't be an issue. |
