Custom Query (202 matches)
Results (49 - 51 of 202)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #149 | fixed | Change error handling for non-CAPE-OPEN errors on interface adapters | jasper | jasper |
| Description |
Interface adapters currently forward non-CAPE-OPEN errors (e.g. COBIAERR_NullPointer, COBIAERR_InvalidArgument) as CAPE-OPEN error with scope, interface name, etc and default error text for the non-CAPE-OPEN error. Error messages become shorter and cleaner if non-CAPE-OPEN errors are simply forwarded as non-CAPE-OPEN errors. |
|||
| #158 | worksforme | Check that code generated code compiles with most up-to-date C++ standards | jasper | jasper |
| #2 | worksforme | CheckEquilibriumSpec | michelpons | michelpons |
| Description |
The COBIA PME is a demo with a limited scope. For instance the GUI enables a simple TP flash to take place but does not allow all the different kinds of equilibrium calculation one can think of. Fine with me. It fits with the demo aspect of the COBIA PME. Still CheckEquilibriumSpec? is called on a Property Package for all the possible combinations or sort of that can be thought of. I think this is an overkill for a demo. For sure nobody sees it happening except when logging the communication between a COM PMC and the COBIA PME. Is there really a purpose for checking all the possible combinations? |
|||