Custom Query (122 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (70 - 72 of 122)

Ticket Resolution Summary Owner Reporter
#48 fixed No error log on Item from Collection Michael Halloran michelpons

Reported by michelpons, 14 years ago.

Description

In PRO/II 8.3 the items of the Port Collection of a Unit Operation has successively called starting at index 0 or index 1. Consequently, if the collection index starts at 1, a call to Item requesting Item 0 returns an error (0x80040501) when for example it is COUSCOUS PropertyTester UO that is used. The log file does not show any attempt by COLTT to interrogate any further the error handling methods of the Port Collection. I thought it was a general practice to do so however.

#50 fixed AspenTech: COLTT does not handle undefined double values? Michael Halloran michaelhalloran

Reported by michaelhalloran, 14 years ago.

Description

COLTT appears to have trouble handling value which is “CapeDoubleEmpty - it crashes. For example, if a requested property (from CalcProp) is unavailable CalcProp() will set “CapeDoubleEmpty” by calling SetProp() and COLTT will crash.

Running COFE(COCO 1.16) with COLTT 1.07 or 1.06.03 enabled and Aspen CAPEOPEN 1.0(Aspen Properties 24.0):

Selected “Default” package:

Clicked on “Liquid properties”, it crashed (COFE closed). From log file you would see: MaterialObject <1> : Call to SetProp :

Property Phase--- Basis--- Calc---- New value pH Liquid (null) mixture -179769313486231570000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000.000000000

#53 fixed Recursive view of Call to get Option list in Viewer michaelhalloran michelpons

Reported by michelpons, 14 years ago.

Description

The attached log file has been obtained with the 1.08.4 where DLLs have been superseded with the ones released on June 30, 2010. The scenario pertains to ticket #32. When looking at the log file with the Viewer and going at the last line displayed, expanding it, going to the last line, I get the same line as before. I can go on and go expanding the last line and apparently displaying the same sequence again. Looks odd to me.

Note: See TracQuery for help on using queries.