View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0008286 | MMW v4 | Install/Config | public | 2011-08-25 04:35 | 2011-09-16 23:43 |
| Reporter | rusty | Assigned To | |||
| Priority | urgent | Severity | major | Reproducibility | always |
| Status | closed | Resolution | no change required | ||
| Product Version | 4.0 | ||||
| Target Version | 4.0 | ||||
| Summary | 0008286: MM Portable: File associations are enabled (regression) | ||||
| Description | Upon installing build 1423 in portable mode, various file associations were enabled by default in the OS Integration portion of the install wizard. This regression was introduced in build 1423 (in previous builds, all OS integration options were unchecked when installing in portable mode). | ||||
| Tags | No tags attached. | ||||
| Fixed in build | |||||
|
|
Rusty, this doesn't seem to be a regression. It looks that you have installed both standard and portable version of MM on the same computer and thus it just shows the extensions that are already associated with MM on that machine (based on registry values). If it wouldn't show them then user could accidentally unassociate all the extensions by using the portable version on that machine. |
|
|
That may be the case, but does it make sense? 1 i.e. Install MM instance A (regular version) to a machine --> File associations trigger instance A to run 2 Then install or plug-in instance B on USB drive --> File associations from Step 1 are checked off, even though the associations are re. Instance A --> File associations are switched to instance B!! i.e. For Portable mode installation and post-install on any version, shouldn't MM only check off those associations relevant to the instance of MM that is running? |
|
|
The problem here is that the file associations aren't per instance. i.e. if MM portable is running and you double-click a MP3 that was associated by regular version it is opened in the running (portable) version. |
|
|
OK--so we can resolve as NAB as long as this won't cause the installed version of MM to lose its associations. |
|
|
I don't know what you mean by NAB, but resolved as 'no change required'. |
|
|
As Ludek posted in 0008286:0027346 his is desired behavior. I see no bugs here especially as forcing Single MM instance |
