List of non-compliances between different release
Here below are listed the non-compliance existing in upgrading a version to new version. The non-compliance require the manual intervention of the programmer in order to get a correct execution of the upgraded version.

Date

Version

Non-compliance Movicon 11.3

21/02/2012

11.3.1101

Integer floating point values can now be formatted for the Meter, Trend and Data Analysis objects as well.

 

Incompatibility:

No conversion management has been setup for projects deriving from previous versions, and therefore these projects may display different integer values.

 

 

 

Some problems have been resolved in recording trace comments that would get kept in memory and then inserted in the next recordings that were not preset for user comments. In addition when enabling the recording on event in the System Log table, the contents in the "Comment" and "Description" columns would invert.

 

Incompatibility:

Enabling a variable Trace event recording in the System Log table, the "Comment" and "Description" columns now result inverted in respect to before.

 

 

 

Column and row resizing would not disabel in the Grid object when the "Show Control Window" was active.

 

Incompatibility:

The grid object "Show Control Window" option is now used for choosing whether to resize the columns in runtime.

 

 

 

Win Wrap Basic Scripting engine updated to the 9.3. version

 

Incompatibility:

A problem with the "Format" function used by the WWB.NET has been remedied. This function would be wrongly executed in the COM context instead of VB.NET. It is for this reason, that when now executing a project deriving from previous versions and according to which function being used, an error may generate or the end result will not be the same as before. Therefore it will be necessary to readapt the use of the function's code.

 

27/03/2012

11.3.1101.4

When an Embedded Screen or TAB Group was used in a Parent project to display a Child project screen, the commands of this screen would execute within the context of the parent project and therefore would not work correctly above all if there were several Child projects which had the same names within the same parent project (i.e. screen names). These commands are now executed by first searching for the resource within the Child project context.

 

Incompatibility:

The resolution to this problem may create malfunctions in projects from previous version in cases, for example, where the command executed by the Child Project have been "adapted" for working around the original problem.

 

31/07/2012

11.3.1102

When an Embedded Screen or TAB Group was used in a Parent project for displaying a Child screen, the command of these screen would execute within the context of the Parent project and therefore would not function correctly above all if Parent project had several Child projects using resources with the same name (i.e. screen names). These commands are now executed by searching the resources first in the Child project.

 

Incompatibility:

This fix may cause problems in projects from previous versions in cases where, for example, commands executed from Child projects have been "adapted" to work around the original problem of this case.