|
ID
|
TOPIC
|
PROBLEM SOLVED
|
|
3570
|
Screen Objects
|
When editing screens in zoom mode, all the screen objects would display with the wrong sizes and positions once the project was saved.
|
|
3546
|
Events Resource
|
In nesting modal screens, Movicon also consented to closing screens that weren't active at that moment. Following this, the modal screens would not close, freezing the project's user interface.
This problem would only show in cases where the nested modal screens were closed using logic, or script functions from the moment when the modal screen, placed in foreground, could receive commands directly with the mouse.
|
|
3579
|
Screen Objects
|
Movicon would go into error and close when object dynamic properties where set from basic script code on the 'SymbolLoading' or 'SynopticLoading' event. This problem would show only when properties set from code had not been set in development mode.
|
|
3531
|
Documentation
|
The online help wrongly stated that alarms could be set in more than one are using the ";" character.
|
|
3539
|
Screen Management
|
Modal screens would sometimes not close. As a consequence, the application had to be restarted in order to make it work correctly. This problem started happening when the Movicon 10.1 954 Build was implemented.
|
|
3474
|
Screen Objects
|
Symbols linked to external configuration '.sxml' files would not get initialized correctly when this file was loaded in runtime. The problem was caused by initializing symbol elements that weren't managed correctly and if these elements contained animation, the following problems would occur:
a) Movicon would go into error and close upon animation variable value change
b) Animations managed in symbol elements were not coherent with the variable value to an extent that the variable would not change value
|
|
3476
|
Screen Objects
|
Object ".sxml" configuration files would not get saved every time screens containing these objects were unloaded from memory. Now, these files are saved only command and when Trend pen properties are modified or when using the VBA function predisposed for this purpose. This problem started happening with the Movicon 11.0.1010 version.
|
|
3479
|
Screen Management
|
The 'Numeric Pad' and Alphanumeric Pad' would get repeated when the window with the pad was closed. This problem would only arise when the command was set with button pressed down or hot region, or using displays with "Prompt Numeric Pad" option.
|
|
3502
|
Screen Objects
|
Alarm window would show incorrect times in the 'Time ON', 'Time OFF', 'Time ACK' and 'Time RESET' columns. These times were incorrect because they did not cater for legal time changes.
|
|
3504
|
Screen Objects
|
Some Movicon objects (Alarm Window, Data Logger Window, TraceDB Window, Chart, Trend and Data Analysis) would not show the correct times when connected to a network Server, when legal time changed (ie. 10th April 2008). The UTC time conversion to local time did not take legal local time changes into account.
|
|
3444
|
DOM (Document Object Model)
|
The 'GetSelectedAlarm' method from the 'AlarmWndCmdTarget' interface would not return 'AlarmThresholdCmdTarget' type objects. As a consequence, the next returned follow on code would generate an "Incorrect Type" error.
Dim objAlarm As AlarmThresholdCmdTarget
Set objAlarm = GetSelectedAlarm
This could be worked around by declaring the object in a more generic way:
Dim objAlarm As Object
Now, the 'GetSelectedAlarm' returns the 'AlarmWndCmdTarget' data type correctly.
|
|
3458
|
Design
|
Project Download and Upload would fail using the TCP plugin in cases which the IP address was used first then the name of the connected device's network. This occurred when these operations where done while remaining in the same Download/Upload window and not closed before the next download/upload.
|
|
3465
|
Accelerator Resources
|
An accelerator which had been disabled through its enabling variable would still accept vocal commands through the Speech Recognition feature.
|
|
3466
|
Screen Management
|
When a screen activated for viewing, it would not adapt to the Movicon window sizes. This problem also occurred with screens pre-loaded at project startup. This problem began with version 11.
|
|
1785
|
WinCE OS
|
The password entry window would not show in PocketPCs.
|
|
3387
|
Screen Objects
|
When clicking a display with the "Prompt Numeric Pad" option in a screen opened in modal mode, the numeric or alphanumeric pad would open twice.
|
|
3391
|
Design
|
When the snap had not been set in the grid, the object's movements corresponding to the 'Undo' command were not memorized causing it to not work correctly.
|
|
3438
|
Accelerator Resources
|
A Shortcut resource's 'Wait Speeching Time' would set with a value higher than 255, even though the one proposed for default was 3000. This value would not stay as it but decrease when the shortcut was deselected and reselected. This value would still behave in the same way when changing it higher than 255 manually.
|
|
3428
|
Screen Management
|
The 'Zoom To' command from the predefined Movicon CE menu would not work.
|
|
3217
|
Design
|
The list of the renamed resources would not change until the project was saved. This would cause a few small problems when project developing.
|
|
3422
|
User Interface
|
In Movicon CE, in a screen with many vectorial objects, the interactivity with clickable controls was very slow. This inconvenience would arise when using controls, such as buttons, combo box, check box and meters etc. This stopped happening when deleting these vectorial objects from the screen. This problem started happening with the version 11 when controls were done in objects to see whether they were overlapped with other objects, in order to execute a command only on the object in the foreground. This control has been eliminated.
|
|
3455
|
Design
|
Drag and dropping screen, accelerator,menu script and parameter file resources would also be consented in resource groups to which the selected resource did not belong. As a consequence, the selected resource would not be added to the intended destination group and would get deleted from the project.
|
|
3483
|
Accelerator Resources
|
It was not always possible to use an accelerator Speech Recognition for supplying string variable set values. Values would be considered invalid when voiced through the microphone when the 'Alphanumeric Pad' command was not set with a maximum char. number. Now when a maximum char number is not set in the "Alphanumeric Pad' command, variables with strings of any length can be set using the microphone as which is also possible when using the Alphanumeric Pad as well.
|
|
3533
|
WebClient
|
It became impossible to put into to order window object lists or column sizes from the Web Client. All mouse actions on the column headings would not longer take effect when done from the Web Client. This problem started happening with the Movicon 10.2 build 956.
|
|
3526
|
Screen Objects
|
When using the keyboard to select combo box list items and pressing the enter key, the linked numeric variable would not update with the selected item's index.
|
|
3509
|
Setup
|
The basic script engine is installed in "C:\Windows\System32" instead of the Movicon installation folder. This has been purposely done to prevent errors from occurring using the same computer with different Movicon products (ie. Power HMI), which always use the same version of the same basic script engine.
|
|
3577
|
Screen Management
|
Movicon would generate an error and close, when closing screens with the "Spawn Thread Execution" option. This error occurred only if the screen name had not been specified in the command. This problem started happening with the 11.0.1010 version.
|
|
3545
|
Design
|
Variable or resource copy-paste operations would not take into account any renamed variables or resources. As a consequence a new variable/resource would get pasted with a name which would invalidate the previous renaming operation.
|
|
3548
|
Screen Objects
|
It became impossible to edit in a grid object using the mouse only. This would cause problems when using this object in the touch screen environment.
|
|
3560
|
Design
|
The TCP plugin would not always create a correct link after exporting a project to a Windows XP/VISTA desktop computer.
|
|
3575
|
Design
|
The TCP plugin would not continue deleting compact flash contents if a file resulted inuse from an application on the device. It now passes on to the next file when errors occur.
|
|
3582
|
Design
|
The Windows registry 'Platform\DeviceExecutable' value would not get managed correctly.
|
|
3605
|
WebClient
|
The Web Client html page would not install a non updated JAVA runtime engine. As a consequence, the JAVA engine has to be updated before connecting from the Web Client with a Server project run with Movicon.
|
|
3629
|
Comm.Drivers
|
The driver selection window did not indicate which communication drivers required a Progea license.
|
|
3535
|
PowerHMX
|
The error message which appeared when selecting the "Run in other Process (Safe Mode)" the "Script" category was not completely correct. In addition, the command selection window would close after the command was confirmed.
|
|
3542
|
Screen Objects
|
The alarm window's 'S' accelerator key would not work, impeding the use of the keyboard for changing the alarm window's sound status.
|
|
3480
|
Documentation
|
The Windows configuration registry 'OPCBrowse->UseRegistry' key was documented incorrectly.
|
|
3475
|
Design
|
The "Generate Unique File Name" command from drawing property windows would not mark the screen to be saved containing that drawing.
|
|
3495
|
Setup
|
The Movicon setup in English would install an non updated 'GenericDriver.chm' file.
|
|
3497
|
Design
|
The drawing property window command used for loading the external configuration file would not mark the project and the screen containing the drawing for saving.
|
|
3470
|
PowerHMX
|
The Trend area could not be printed when using PowerHMI. In fact the print button was missing and therefore could not be used in the object.
|
|
3425
|
Setup
|
The following problems relating to the Movicon 11 setup of 26/03/2008 have been solved:
1)Custom Installation: when selecting Italian as installation language, some texts that identified components were in English while others were in Italian
2)Custom Installation: the TCPUploadServer.exe file was not associated to the “Upload-Download Manager” component
3)custom Installation: the "User Dialogs" component from the symbol library would still get installed that library even when disabled
|
|
2343
|
Report Management
|
Using the data filter in the window, proposed after invoking the report category's "Data Analysis" command would not work correctly.
|
|
2344
|
Report Management
|
The 'DataChart.exe' print command would print two pages: one with the chart and one with the data table. On the first page, the chart would not get adjusted to screen page sizes and therefore not all of could be seen.
|
|
3430
|
Schedulers Resource
|
A project run would always show an error message when the '\DATA\rtsched.xml' file was missing. This file would only get added to the project when inserting a scheduler in runtime, but the error message would show nevertheless, independently with or without the presence of a scheduler. The message now shows only when the file is present but not readable. It will not show if the file does not exist due to the fact that a runtime scheduler object has not been inserted.
|
|
3435
|
Design
|
The 'Check for updates' command in the About window would not get managed correctly.
This command could only be used for signalling the availability of a new project version, and not of a new project build.
This command now also checks for builds and the message displayed is as follows:
The program version being used is the 'current version'. A newest version is available. Do you want to see more information?
|
|
3436
|
Design
|
The 'check for updates' command from a driver property window would not get managed correctly (see case 3534 for the same command in the Movicon About window). The message shown has been changed and now proposes the user to:
The driver version being used is the 'current version'. A newest version is available. Do you want to see more information?
|
|
3437
|
Design
|
The "Check for Updates" command in the Symbol Library would not work correctly.
|