GetCompoundConstant logs without values

[michelpons]

I am using the CO-LaN Property Package prototype in version 1.1 as a plug in Aspen Hysys 7.2. I am puzzled by the following: after a number of CheckEquilibrium calls, Aspen Hysys makes a number of GetCompoundConstant calls on the Property package. While in OATS, argument values of these calls are logged, in the COLTT log, no value of arguments is shown. Also, perhaps to deliver in the log the list of compounds, COLTT makes calls to GetCompoundList on top of what Aspen Hysys is requesting. These calls are returning an error.
This run has been made with the version built on Aug 16, 2010. I attach the log obtained with COLTT as well as the one obtained with OATS.

[michelpons]

Log file obtained with COLTT built Aug 16, 2010

[michelpons]

Log file obtained with OATS

[michelpons]

I have tested the case with COLTT 2.1 Build June 5, 2012. I see a difference in the log file where now the following lines are showing up within the logging of a GetCompoundConstant:

PropertyPackage <Anonymous> : Call to GetCompoundConstant

GetCompoundConstant takes Input Arguments:

COLTT <Anonymous> : Call to GetCompoundList
COLTT <Anonymous> : Error returned from GetCompoundList - 0x80040501

Warning - compIds argument is empty

GetCompoundConstant returns:

Property Compounds ValueReturned

PropertyPackage <Anonymous> : Return from GetCompoundConstant - Succeeded

There is now a warning message about the compIds argument being empty. I still don't agree with the way it is handled. Before making the call to GetCompoundList, why isn't there a print at least of the property name? Same following \"getCompoundConstant returns:\", could we have the property name printed, something like \"EMPTY\" or \"UNDEFINED\" under \"Compounds\" and the vector of returned values printed?

[michelpons]

Log file obtained with COLTT 2.1 Build June 5, 2012

[michaelhalloran]

Resolved by the fix to #16. Available in builds after 21 July 2012.