|
ID
|
TOPIC
|
PROBLEM SOLVED
|
|
1068
|
Screen Objects
|
The application would raise an exception when managing design animations on screen under certain conditions.
|
|
1542
|
Networking
|
Network Client projects would freeze up with the hourglass on screen, load pages which contained variables to be connected to the Server. This problem was introduced with 952 build, but could be avoided by disabling the UDP protocol.
|
|
308
|
Screen Management
|
Application would go into error and close when screens with active "Spawn Thread Execution" options were loaded. This would happen when the screen had objects receiving inputs from the mouse.
|
|
1656
|
License
|
Incompatibility:
Softkeys must be reentered after updates. The 955 build introduces changes that may impede code from being cracked.
|
|
1661
|
WinCE OS
|
MovXCE would go into error changing pages when the page close screen delay times were set at zero. Now the WinCE version behaves like the desktop as well, when the screen unloading time is set at zero. Therefore unloading screens previously loaded from memory may take longer.
|
|
1662
|
Screen Objects
|
Network Server historical data would show the wrong times in Network client window objects. This would happen in days coming up to and after the day where the legal daylight saving time changed of the time zone set in the Network Server.
|
|
1660
|
Networking
|
Variables could not get connected to the Network Server without enabling the Inuse Variable manager (realtime database option). Therefore all the variables' networking would not work. Now they work without the Inuse variable manager by being connected automatically to the Network Server at project startup.
|
|
663
|
WinCE OS
|
the file containing the runtime user settings would not get reread by MovXCE, when it changed making it impossible to get hold of the new runtime user settings without having to restart the project. Now, only in WinCE, MovXCE controls and rereads any changes every 2-3 seconds.
|
|
1312
|
Networking
|
Variables connected to a Backup Server, through their "Backup Server" properties, would remain disconnected to the variable on the Network Server, even when in use. This would happen following a page change and in certain other situations.
|
|
1543
|
Design
|
The project folder would not delete on the device after being uploaded to WinCE with the TCP plugin if the CEUploadServer.exe service was not terminated beforehand.
|
|
1545
|
WinCE OS
|
MovXCE would not read the SINGLE_PATH_SEPARATOR and DOUBLE_PATH_SEPARATOR parameters saved in the "<Project>.movrealtimedb" resource. As a consequence, problems would arise with the OPC client (only in WinCE), when these parameters were not the same as the "\" and "\\" default values.
|
|
1469
|
Design
|
The TPC plugin would not upload projects correctly under certain circumstances. The upload would terminate successfully but the project resources would not get saved on the device correctly. Therefore when running the project on the device, errors would arise when reading the xml. resources. This problem has now be solved and a CRC control has be inserted to ensure that the resources save in the device are the same as those on the desktop.
Incompatibility:
-
The "CETransfer.dll" file must be the in same version on the WinCE device as well. If it is not the same as that on the desktop, it might be uploaded unsuccessfully
-
the "CEUploadServer" service's communication thread on WinCE has been given more Movicon Runtime priority. Therefore any project being run may be slowed down by the upload in progress
|
|
1524
|
Design
|
Errors would arise and close the Movicon application when working in development mode with ActiveX. This problem would only happen with those ActiveXes which gave out notifications of unexpected or unusual changes. For instance, when nothing had changed on screen. The operations which caused this involved copying ActiveXes on screen or trying to insert them into the library.
|
|
1553
|
Basic Scripts
|
ActiveX TeeChart events were unusable. Now all events not requiring mouse interaction can be used. Those that do require mouse interaction remain unsupported for product stability reasons: modifications may make those ActiveXes already working well with Movicons unusable.
|
|
1463
|
WinCE OS
|
When a IMDB exceeds a certain size, around 2MB, an error would arise in the application causing to close. This would only happen when using devices with Windows CE and microprocessors belonging to the ARM family.
|
|
1615
|
Networking
|
Some variable would not connect to the Network Server when Loading pages into Network client projects. These variables would therefore not be updated with the current values in the Server. This problem would arise with those variables which were set in the screen's controls when loaded with the basic script interface.
|
|
1651
|
User Interface
|
Movicon would raise an error at startup, when unable to recognize the network card type installed on the computer. This control check has been by-passed and is no longer carried out at the start-up.
|
|
1652
|
WinCE OS
|
The write of the IMDB data logger file would send MovXCE into error. This prolbem would arise because the write of the XML file used the process's memory and when the 32MB max. limit was exceeded, the operating system closed the application. The shared memory is now used and which is limited by the IMDBMaxHMemory value of 4MB for default.
|
|
1636
|
Screen Objects
|
Image transparency was degenerated when managed in bitmaps exceeding a depth of 8 bits.
|
|
1567
|
WinCE OS
|
The SQL Server CE databases would not compress at project startup. As a consequence, their sizes would be out of proportion in respect to their data volume contents due to the fact that they still contained deleted records.
|
|
1577
|
Design
|
Project unloading would fail when the device's CPU was overloaded work. The TCP communication thread manager is now instantiated with high priority to stop communications going into timeout.
|
|
1584
|
PowerHMX
|
PowerHMX only enabled one communication driver in demo mode. It now enables two.
|
|
1592
|
WinCE OS
|
The "MaxAvailVirtual" key manager has been modified. The "MaxAvailVirtual" key is used for managing the unloading of screens when the MovXCE application has insufficient memory space for running the application. MovXCE enters into low memory condition for the following reasons:
-
When the "MaxAvailVirtual" value of the memory used by the process nearly reaches the maximum value allowed by the in operating system in use (32 Mbytes for WinCE 5.0, 2 Gbytes for WinCE 6.0)
-
When the total memory available for programs goes below the level defined by the "MaxAvailVirtual" value. When MovXCE is in this condition the opening of a new screen will force the first loaded screen to unload from memory. Furthermore script executions may be denied for the same insufficient memory reason
|
|
1605
|
Design
|
Symbol dropping code would not manage VBA expressions inserted in controls correctly. Variables with the name of the expressions would get added to the project. Movicon now recognizes each single variable used in each expression and inserts them in the project when the symbol is taken from the library and added to the screen.
|
|
1633
|
Design
|
Variables used in symbols could not be replaced with others already existing in the project by dropping code. The "OnVariableCreating" event's "VariableName" parameter can now be used for modifying names of variables used in symbols. This event is, however, managed only when the dropping code is executed when symbols are inserted on screen from the library.
|
|
1546
|
Design
|
Screens would get saved in projects with the zoom level applied to the screen during development mode. As a consequence the screens' objects would no longer display in their original sizes in runtime.
|
|
1362
|
Redundancy
|
The persistent historical data manager used up a lot of memory in redundancy mode. This problem arose from the fact that only one persistency file was used and that this file was saved compressed. When recordings became very frequent this file would adapt to accommodate them and therefore required more memory. Two new properties have now been added to set the maximum number of files with the maximum number of recordings they can hold.
|
|
992
|
Design
|
The object count would take up too much time in screens containing a lot of objects. This has now been speeded up by half in size order. This may have also caused problems opening screens in edit mode which contained Active X objects, such as the TeeChart, where the screen would open completely empty.
|
|
1000
|
Design
|
The window used for exploring dynamic symbol properties would not display all the variables used in them. The list of variables, set in some of the symbol fields such as the 'move to variable' command field, would not show.
|
|
421
|
Design
|
The IL Logic of objects could not be compiled if screen local variables had been used. When the compiler found one of these variables it would raise a error claiming that variable could not be found. This problem only happened in development mode but not in runtime where it worked correctly. This problem was partly solved with the 950 build but remained unsolved for the structure variables which were having the same problem.
|
|
217
|
Design
|
When symbols inserted variables associated to variable groups, these groups would display in the realtime db only when the project was reopened.
|
|
218
|
Design
|
Local screen variables would display within variable groups in the project explorer window. These local screen variables are now displayed separated from the variable groups.
|
|
883
|
Design
|
Button object execution options were not very userfriendly to set when it came to selecting their mechanical function type. A dropdown list has now been inserted in the 'mechanical style' property with a selection of commands such as: "Execute commands", "ON-OFF" and "Impulsive". In addition to this, those properties that have no influence on the function type selected from this list will be automatically disabled.
|
|
973
|
Design
|
Button objects would show illuminated in the ON status when entered on screen in design time. Now, both lights and buttons remain in the Off status, therefore no longer illuminate, when entered on screen in design time.
Incompatibility:
All the coloured lights are now displayed in grey in design time. To distinguish their colour when illuminated in the ON status you will need to go to their properties window and see the corresponding style option.
|
|
1103
|
Networking
|
The reconnection of variables towards the Backup Server, or viceversa, would take up too much time when their were lots of variables to be connected. A new Server black list in timeout management has been inserted which halves the time needed before in reconnecting variables.
|
|
1541
|
Setup
|
The PATH variable is no longer set with the path with which the CRTool was installed. This operation became pointless after the CRTool was eliminated from the tool menu.
|
|
1561
|
WinCE OS
|
The MovXCE startup screen showed "Script Engine Installed" written without the "n" character in "installed".
|
|
1644
|
PowerHMX
|
PowerHMX would take recipes into account when limiting the maximum number of data loggers to be initialized. The 2 data logger limit no longer regards the recipes which have no imposed limit on the number that can be used.
|
|
1589
|
WinCE OS
|
The "General->ILSleep" value has been set for default at 50 milliseconds for WinCE. The old default value was 10 milliseconds. The new value allows more CPU resources to be freed in projects using IL logic, above all in those devices which have slow CPU. This should help the user interface work more smoothly.
Incompatibility:
The IL Logic will be processed more slowly. In cases where the same execution velocity is needed as before, you will have to set the General->ILSleep key value back to 10.
|
|
1596
|
Design
|
The default structures associated to symbol items would not change when using the the window to browse the dynamic symbol properties.
|
|
1598
|
Screen Objects
|
The "requery" method from the "TrendCmdTarget" interface would not populate the run buffer with historical values. As a consequence, historical data could not be seen in the first trend page in run mode when changing the data logger linked by means of a basic script. This buffer is now only filled with historical values when the trend is in run mode.
|
|
1580
|
Networking
|
Information in the Network Server log (the optional one), was not saved correctly making it impossible to get hold of the right information efficiently due to missing data, ie. names of the variables.
|
|
1680
|
Setup
|
The AlarmDispatcher would install launching an embedded set-up within the Movicon set-up. This would cause problems in certain situations, such as the case with Windows Vista. Each individual File is now installed in the Movicon "AlarmDispatcher" subfolder.
|