get_requestedOperation

[michelpons]

In the attached log file, it is unclear what the call to get_requestedoperation means. The Property Package receives such a call apparently but on which interface. This is unclear. Should be clarified. I attach also what the Viewer looks like for that call. It is rather cryptic.

[michelpons]

Zipped log file obtained with COLTT 2.0 as released

[michelpons]

Zipped RTF file containing screenshot obtained with Viewer 2.0

[michelpons]

Log is obtained by using PRO/II 9.1. A new case is created where the PP nC6nC8nC10 of IdealVB6 Thermo System is used. A single material stream is created with partial mass flowrates in kg/hr defined (1 for nC6, 2 for nC8 and 0.1 for nC10), temperature as 40°C and liquid fraction as 0.5. The single stream is flashed.

[michaelhalloran]

get_requestedOperation is a method on the ECapeBadInvOrder error interface. It seems that PRO/II is correctly calling the error interfaces following an error returned by the PMC, but the PMC does not implement the error interface methods correctly since none of them return any useful information. In fact though the error returned is not a CAPE-OPEN error and is not recognized in Visual Studio's Error Lookup tool.

Only a few methods in COLTT log files are prefixed with the name of the interface they belong to. Is it a general requirement to report the interface name for each method?

[michelpons]

For most methods who are commonly used in CAPE-OPEN interfaces, I have no problem figuring out what is the interface they belong to. It is with methods less often used like this one that I get confused. I think a general requirement is indeed to be as precise as possible in the rendering of information. Now this has not a high priority because the information may be found by other ways. Still having to scan the IDL or the specification documents is not that great even if it may bring light on some other stuff when going through the specs.