|
ID
|
TOPIC
|
PROBLEM SOLVED
|
|
9013
|
Basic Scripts
|
The bit 2 of a basic script's status variable would not get managed if script had an error. The bit 2 is now changed to 1 if an error occurs and remains at 1 until the error window, opened by the script, is confirmed. When the error window is closed, the bit is zeroed.
|
|
9033
|
Data Loggers Management
|
When restoring the ODBC connection after an error, the status of a Data Logger variable would remain set with value 1 instead of returning to value 0.
|
|
9000
|
Data Loggers Management
|
A Data Logger's status variable would not get saved in the Data Logger file and therefore this setting would be lost when the project was next loaded. Furthermore, when setting the project with a Basic license, the status variable became impossible to set in the recipe resources.
|
|
8961
|
Design
|
In certain conditions the ".movrealtimedb" file would get saved without its contents while the project was being saved. In addition to this, the project would remain in the "not saved" status even though it had been saved.
|
|
8947
|
License
|
When using a "Basic" license, it become impossible to manage the Trend object became impossible to manage correctly would no longer show data in runtime.
|
|
8966
|
OPC Communication
|
A project set for connecting to one or more OPC Servers would generate a misleading error message in the Log when one or more OPC Servers were unavailable at project startup. This message has now been modified and when setting the "Reconnection Time" to '0', Movicon will no longer attempt to connect to Server if first attempt failed.
|
|
8944
|
Real Time DB
|
When using an array type variable connected to a Communication Driver and one or more of its elements went into use for the first time, the Driver would nevertheless write the array variable even though its value had not been changed.
|
|
9009
|
Real Time DB
|
When user expanded a structure variable in the Watch window to view the values of its members and then changed to and back from another tab, the initial structure member values would display set to '"unknown".
|
|
8955
|
Recipes Management
|
When Float Array variables were used in a Recipe object, the decimal part would get lost when values were loaded from the database.
|
|
9035
|
Recipes Management
|
Some Recipe status variable bits would not always function properly.
|
|
8941
|
Screen Objects
|
In certain cases there were problems in managing ListBox objects when partly overlapped with other ListBox objects. This has now been fixed and will work correctly providing that the "Show Control Window" remains disabled.
|
|
8973
|
Screen Objects
|
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.
|
|
8991
|
Setup
|
The SetUp would stopped installing "Movicon.ini" file.
|
|
9041
|
Setup
|
The WinWrap 9.3 version installation warning message was unclear and now has been updated to be more explicit.
|
|
8943
|
Setup
|
The SetUp would erroneously install the "WWB9@000.dll" file which would cause problems displaying dialog windows in Windows 7.
|
|
9021
|
Setup
|
The DEMO projects had not been enabled with the Network Services and therefore could not connect to Web Clients without modifying project beforehand.
|
|
9023
|
WinCE OS
|
Movicon would not startup correctly in Windows CE 7 operating systems.
|
|
8983
|
WinCE OS
|
The "ActiveScreen" system variable would not update correctly in Windows CE when the screen was opened as a PopUp.
|