Wrong debug information due to wrong include of MFC replacement classes

• Related Articles

• Alarm areas: wrong value of status variables of linked Alarm Classes when number of alarms exceeds the size of ring buffer

  Summary If the number of alarms exceeds the size of the ring buffer, the status variables of linked Classes in Alarm areas are calculated wrong. Description If the number of alarms exceeds the size of the ring buffer, the status variables of linked ...

• LM (former EMS): misleading information when user manually enters wrong min/max switching times.

  Summary Issue in Load Management when then user edits the switch-on/off time and makes min value bigger max value: no warning message during compilation of project. In the Runtime wrong configured component is treated like switchable and comes along ...

• Numerical prefixes of Alarm groups/classes/areas are not correctly sorted in AML filter

  Summary Alarm groups/classes/areas in lists in AML filter are sorted as text. But as they starts with the number (property "No.") the order is not correct: 1, 10, 11,..19, 2, 20, 3 etc. When converted to string the numbers 1..9 should have leading ...

• zenon Changesets Excel

  Here, you can access a comprehensive list of changes across all maintained versions of the zenon Software Platform as Excel Worksheets. This includes both implemented bug-fixes and new features. Additionally, these lists are available in CSV format ...

• Under specific circumstances the XML-import of alarm areas result in a wrong class linking in the editor.

  Summary It may happen that the XML-import of alarm areas between two sub projects result in a wrong alarm class linking in the editor, so that the alarm areas class linking in the target sub project are shifted to the next alarm class, previously ...