|
Date
|
Version
|
Non-compliance Movicon 11
|
|
26/03/2008
|
11.0.0.1010
|
An option to create a configuration file in which a series of settings can be saved so that they can be restored, using an appropriate command, for future use has been added to all screen objects.
Incompatibility:
In certain cases where external file haves already been used in the project for Trend object settings, it may be necessary to re-save the screen containing the object in question with Movicon 11 to ensure that it works in the same way as before.
|
|
|
|
The dynamic tooltip has been set at "false" for default for all objects. Therefore when you insert a new object on screen, the dynamic tooltip will not get set for default.
Incompatibility:
A ver. 10.x project when run with the 11.x version will not display the dynamic tooltip in objects which displayed it beforehand. To display the tooltip you will need to open the project in design mode and reset the option for showing the dynamic tooltip.
|
|
|
|
The first day of the week for the "Scheduler" object is now Monday instead of Sunday. This is converted automatically when passing from the 10.2 version to the 11.0 version but the inverse is not guaranteed.
Incompatibility:
Once a project has been upgraded to the 11 version, the schedulers may activate wrong time plans if launched with the previous Movicon version.
|
|
|
|
The "Scale Min." and "Scale Max." scaling values in the variable Data Engineering properties, are used by some object to define their scales. These objects set their own scale based on these variable Data Engineering settings, only when the variable's Data Engineering 'Enable' property is active.
This management is currently supported by these objects:
-
Display
-
Spin Buttons
-
Standard Gauges
-
Trend and Data Analysis
It is not yet support by these objects:
-
Dundas Gauges
-
Numeric Pad
Incompatibility:
The above mentioned objects which used variables whose Data Engineering has been enabled by mistake, will use the min. and max. limits set in the variable and not those set in the object's properties. To restore the object back to its correct working state you will need to disable the Data Engineering option if not needed, or set the interested variables' Data Engineering scale properties in the same way.
|
|
|
|
The "Record On Change" would activate every time a variable changed. Now as for the "Record On Time Frequency", the "Record On Change" takes into account the Datalogger's enabling variable, variable qualities and any set time frames.
The "Record On Command" would also record even when disabled and if there was a "Recording variable".
Incompatibility:
when loading projects created with previous versions, the "Recording Variable" will only be initialized if the "Record On Command" checkbox has been checked.
|
|
|
|
Values could not be entered in keys which had different names in the MovXCE.ini file. This problem was due to the fact that a root item was missing from the file's XML definition, which has now been added with the name of <Settings>.
Incompatibility:
MovXCE.ini files created for the 10.2 version must be modified by adding the <Settings> root tag in order to be read by Movicon 11.
|
|
03/07/2008
|
11.0.0.1012
|
A symbol would get inserted from the library into the screen with its original sizes. This symbol now gets inserted on screen with the sizes it was saved with in the library at that moment.
Incompatibility:
Library symbols could be inserted with different sizes by updating Movicon, if they were scaled at the moment they were saved in the library. In this case, symbols need to be resized on screen and then re-saved in the library.
|
|
15/01/2009
|
11.0.0.1014
|
The report designer has been updated and now also supports the option to configure parameters which are proposed to the user when opening a report. For example the user can be given the choice of criteria with which they would like the data filter to be applied to upon executing the command.
Incompatibility:
A report saved with the new report designer can not longer be managed with the previous Movicon build. Any attempts to do so will cause the application to go into error.
|
|
|
|
The report designer continued using the "Table" name as the name of the table and not the real table name in the database. This, however, did not compromise the correct execution of the report.
Incompatibility:
Opening a report created with the previous version, you need to re-assign the table column which now has a new name to each report field.
|
|
24/04/2009
|
11.0.0.1016
|
A 3D button with a "ON-OFF" mechanism mistook the background colour with the text colour when the variable was set differently to zero. This behaviour would make the button's text nearly invisible. Now this button lights up when the variable is set, and the background and text colours no longer get swapped over by mistake.
Incompactibility:
The 3D buttons were set in a certain way so that you could play around with colours so that texts and background colours swapped over with each other. Now due to this new feature to illuminate buttons you may need to reset the back colours originally set with the previous Movicon version.
|