View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0006864 | MMW v4 | Install/Config | public | 2010-12-06 20:14 | 2010-12-08 08:18 |
| Reporter | rusty | Assigned To | |||
| Priority | immediate | Severity | major | Reproducibility | always |
| Status | closed | Resolution | fixed | ||
| Product Version | 4.0 | ||||
| Target Version | 4.0 | Fixed in Version | 4.0 | ||
| Summary | 0006864: MMIP files are not correctly associated | ||||
| Description | Upon a clean install of MM, double-clicking an MMIP file doesn't automatically install it. Tested build 1331. | ||||
| Tags | No tags attached. | ||||
| Fixed in build | 1332 | ||||
|
|
I cannot reproduce it, I also checked over the code and I don't see how this could happen, in addition by default all file associations (including MMIP) are re-associated on every MediaMonkey startup. Could you describe detailed steps to repro, there seems to be something specific. |
|
|
I think that it's related to the change that MM doesn't associate anything on install, only on the first run. I.e. even MMIPs aren't. This should be changed, MMIPs should be associated in the installer (probably by calling MM, as was done in previous versions). |
|
|
I see, you probably didn't launch MM at all, then yes, installer doesn't associate it, but it is associated on the first time run together with the others confirmed/selected extensions. I guess that only the unassociated (no other app use it) extensions and 'mmip' should be associated by installer. |
|
|
Fixed in build 1332. Installer now associates unassociated extensions and 'MMIP' |
|
|
Verified 1332. |
