Reported by michelpons, 13 years ago.

When a call to the Item method on a Parameter Collection occurs the Viewer displays: Parameter Collection <C01> : Call to Item

Parameter Collection Item takes input argument: 1 Item returns : 1 : 0x129247d8

While for an Item method call on a Port Collection, the Viewer displays:

Port Collection <C01> : Call to Item

Item returns : FEED 1 : Ox12922440

So the input argument is missing in the Port Collection display. This has some importance when the Item method call fails. One does not know for the Port Collection which item has been called.

Reported by michelpons, 13 years ago.

There is at least one major commercial PME which is relying, but not only, on IPersistPropertyBag. Logging for this persistence interface is not supported by version 1.08.5 of COLTT. May be worth developing the suitable logger.

Reported by michelpons, 13 years ago.

When analyzing logs obtained with COLTT 1.08.5 with two different PMEs and the same PMC (the CPP Mixer Splitter example), I have noticed that within the Calculate method, the Duplicate method is called twice (because there are two feeds to the UO) and each time the pointer returned appears as the same. This is worrying me because in fact the previous MO is not released before a new duplicate is done according to the following excerpt of the CPP Mixer Splitter code:

bool Duplicate(Material &m,wstring &error) {ATLASSERT(materialObject); class should be instanciated properly create a new material object MaterialObjectWrapper *MO=materialObject->Duplicate(error); <------- NEW ONE IS OBTAINED if (!MO) return false ; fail clean up old MO in m if (m.materialObject) m.materialObject->Release(); <------- OLD ONE IS RELEASED set new m.materialObject=MO; ok return true ;

}

So while this has no consequence really for the CPP Mixer Splitter it is of interest to know if the pointer mentioned in the log is the real pointer or one pertaining to the CO logger. Could this be assessed?