View Issue Details
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0017290||MediaMonkey (current)||Framework: Scripts/Extensions||public||2020-12-26 21:43||2021-01-16 14:47|
|Target Version||4.1.31||Fixed in Version||4.1.31|
|Summary||0017290: Opening MM4 always overrides MMIPs association from MM5->MM4|
|Description||If a user changes MMIPs to open in MM5 instead of MM4, but then opens MM4, it always overrides the filetype association from MM5 back to MM4.|
Solution would be to make the *installer* change file association instead of the program. Preferably, both installers (MM4 and MM5) should have a checkbox for "Associate .mmip (MediaMonkey Install Package) files with MediaMonkey [4/5]", which starts out checked but can be unchecked.
|Steps To Reproduce||1. Set MMIP files to Always open in MediaMonkey 5|
2. Open MM4 (Not via MMIP, but just open it normally)
MMIPs now always open in MM4 instead of MM5.
|Tags||No tags attached.|
|Fixed in build||1915|
Sounds like a reasonable approach except I wouldn't make it configurable at this point:
a) I'm not sure that we'd want to split file association configuration to different locations (i.e. mmip in the installer and media file types in MM --> Windows)
b) Strings are frozen and I think that this fix should be classified as 'urgent' for both MM4 and MM5
I can confirm that MM4 re-associates MMIP and MMDC on each start (once it founds them no longer associated with MM4).
Current workaround is to use MM4 portable version.
- for 4.1.31: Disable this association on each start and do it only the first start after install
- for 5.0: As MM5 addons are not compatible with MM4 addons then we could rather use *.mmip5 as the extension for MM5 addons ?
||Added the MM4 sulution in 220.127.116.115 (i.e. mmip/mmdc is now associated only during MM4 install -- or on the first launch after re-install)|
Ludek implementation from ~61101works if MM4 is installed after MM5 on next MM5 start associations are back to MM5.