Reported by michelpons, 13 years ago.

The message \"COLTT Property Package Final Release\" is printed by COLTT within the log file. This message appears in the Viewer even if all COLTT entries have been asked to be hidden. If indeed it is an information generated by COLTT and not by the components interacting through CO interfaces, may be worth modifying it so that it is also hidden.

Reported by michelpons, 12 years ago.

Using COLTT 2.1 Build June 5, 2012 I noticed in the attached log that many warning messages are written to the log file, within SetProp and GetProp method calls: Warning - compIds argument is empty

I wonder if this is relevant since the compIds argument may be UNDEFINED. Does it mean that the way UNDEFINED is set is wrong wrt the argument type? Is this warning significant with respect to the PMC or is it related to COLTT?

Reported by michelpons, 12 years ago.

I am using COLTT 2.1 Build June 16, 2012 enabled on a TEA Thermo System and a COUSCOUS Mixer in PRO/II 9.1. I start from a case file where the TEA Thermo System and one of its PP has already been declared and two material streams have been defined. Then I drop the COUCOUS Mixer on the flowsheet, connect inlet ports and the outlet ports and then I run the simulation which ends up with no error. Parsing through the log file obtained, I am puzzled by the following sequence:

COLTT <CO1> : Call to QueryInterface

Requested Interface : IPersistPropertyBag

COLTT <CO1> : Error returned from QueryInterface - 0x80004002 COLTT <CO1> : Call to QueryInterface

Requested Interface : IPersistStorage

COLTT <CO1> : Error returned from QueryInterface - 0x80004002 COLTT <CO1> : Call to QueryInterface

Requested Interface : IPersistStreamInit

COLTT <CO1> : Error returned from QueryInterface - 0x80004002 COLTT <CO1> : Call to QueryInterface

Requested Interface : IPersistStream

COLTT <CO1> : Return from QueryInterface - Succeeded COLTT <CO1> : Call to QueryInterface

Requested Interface : IPersistPropertyBag

COLTT <CO1> : Error returned from QueryInterface - 0x80004002 COLTT <CO1> : Call to QueryInterface

Requested Interface : IPersistStorage

COLTT <CO1> : Error returned from QueryInterface - 0x80004002 COLTT <CO1> : Call to QueryInterface

Requested Interface : IPersistStreamInit

COLTT <CO1> : Error returned from QueryInterface - 0x80004002 COLTT <CO1> : Call to QueryInterface

Requested Interface : IPersistStream

COLTT <CO1> : Return from QueryInterface - Succeeded COLTT <CO1> : Call to QueryInterface

Requested Interface : IPersistPropertyBag

COLTT <CO1> : Error returned from QueryInterface - 0x80004002 COLTT <CO1> : Call to QueryInterface

Requested Interface : IPersistStorage

COLTT <CO1> : Error returned from QueryInterface - 0x80004002 COLTT <CO1> : Call to QueryInterface

Requested Interface : IPersistStreamInit

COLTT <CO1> : Error returned from QueryInterface - 0x80004002 COLTT <CO1> : Call to QueryInterface

Requested Interface : IPersistStream

COLTT <CO1> : Return from QueryInterface - Succeeded COLTT <CO1> : Call to QueryInterface

Requested Interface : IPersistStream

COLTT <CO1> : Return from QueryInterface - Succeeded COLTT <CO1> : Call to IPersistStream.Save COLTT <CO1> : Return from IPersistStream.Save - Succeeded

It seems there are repeated calls on the same interface by COLTT and that the failure to find this or that interface on the UO is not accounted for by COLTT which repeats on and on the same calls. This sequence seems to occur several times and since the overall logging takes quite longer than the simulation wothout any log, I was wondering if unnecessary calls were made by COLTT and if so could be discarded.