View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0007119 | MMW v4 | Other | public | 2011-01-04 20:28 | 2011-01-11 03:18 |
| Reporter | michal | Assigned To | |||
| Priority | urgent | Severity | minor | Reproducibility | always |
| Status | closed | Resolution | fixed | ||
| Product Version | 4.0 | ||||
| Target Version | 4.0 | Fixed in Version | 4.0 | ||
| Summary | 0007119: There is COM objects collision, if MM3 and MM4 are running parallely | ||||
| Description | In this case, when e.g. video plugin asks for MM COM object(for reading local and global plugins paths), it is not warranted, it gets the right MM COM object instance (it could get MM3, and subsequently will not find path to DXFilters). Shouldn't we change at least main application GUID - CLSID_SDBApplication? | ||||
| Tags | No tags attached. | ||||
| Fixed in build | 1343 | ||||
|
|
Would not suggest that. It would make problems with scripts and apps that use MM COM. It should be checked for version string. That is same with multiple MM instances from Different folders and set of plugins. |
|
|
As discussed over IM, we really shouldn't change the GUID, we should pass the correct MM interface to the video plug-in (and other plug-ins, where necessary). |
|
|
Fixed in build 1343. Video plugin and AAC plugin now get MM interface using MMCookie, not GUID. |
|
|
Verified 1343 |
