|
ID
|
TOPIC
|
PROBLEM SOLVED
|
|
8453
|
Alarm Management
|
The sound setting of an Alarm Window connected to a Network Server would not get saved when user logged off and when user logged back on this setting would result as disabled.
|
|
8377
|
Alarm Management
|
The Alarm Statistics would not work properly with some of Movicon's installation languages such as Russian, Chinese and Spanish.
|
|
8490
|
Alarm Management
|
In certain conditions in a redundancy system, the Primary Server would keep alarm sounds active even when alarms were not active.
|
|
8386
|
Basic Scripts
|
The script code associated to the Click event of the script enclosed in a screen object, such as a button, would get executed even though the mouse with button pressed down had moved outside the object before releasing button. This behaviour does not comply to Window standards. Furthermore, the double click event of the script enclosed in a screen object, such as the button, would not work correctly if object happened to be rotated.
|
|
8387
|
Basic Scripts
|
The "SaveImageToFile" command from the "SynopticCmdTarget" interface would always return True even when the screen's image was not available and therefore no file would get created. Similar to this, the "GetImage" function would always return True even when the image to be loaded was unavailable.
|
|
8542
|
Data Loggers Management
|
In certain situations the DataLogger would not record when variables were put into use from another resource. This would happen if the "AlwaysInUse" xml tag had been set at zero, even when this property should have been managed bythe Recipe only.
|
|
8401
|
Design
|
The Data Logger "Save CSV file format" option would not get managed by the editor correctly. When this option was modified in one Data Logger it would get propagated to other existing dataloggers.
|
|
8295
|
Design
|
The "Create Symbol" command executed during screen zooming mode would change the font size of object titles incorrectly.
|
|
8450
|
Design
|
In a redundancy system changes made in the runtime user file would not get loaded by the Secondary Server if not active. File would only get loaded when Secondary Server was active.
|
|
7382
|
Design
|
"Resource not found" errors would appear in certain conditions executing the "Save with name" command of a project created with previous versions. This would happen if the tree structure had been expanded beforehand for one of the project's multiple resources, such as Screens, Menus, Accelerators, Basic scripts and Parameter files.
|
|
5863
|
Design
|
Stopping a project after executing scripts in the parent and child projects would generate an error message showing the following text: "No error message available".
|
|
8575
|
DOM (Document Object Model)
|
The "SaveImageToFile" function from the "SynopticCmdTarget" basic interface could not be used in WinCE. This now works correctly but only images in "bmp" format can be created.
|
|
8405
|
Events Resource
|
Events associated to members of a Structure variable from the Parent Project would not get executed.
|
|
8373
|
Networking
|
A Network Client would not receive changes to variables on the Server immediately but only after timeout.
|
|
8364
|
Networking
|
Delays would occur in exchanging data between Network Client and Server projects when the "Local Transport" was used.
|
|
8461
|
ODBC
|
Restoring historical data recorded on text file in cases of ODBC connection errors would get done in the wrong database if the historical log's DSN had been modified in runtime.
|
|
8502
|
ODBC
|
Movicon would go into error when loading a Grid object when this object was connected to a PostreSQL database.
|
|
8307
|
OPC Communication
|
The value set in the "OPC Server Min. Impers. Level" property would not stay the same.
|
|
8240
|
OPC Communication
|
The OPC tag's "ReRead Item" option asked for value from the cache and not from the devise.
|
|
8412
|
Real Time DB
|
The ".movrtmembers" file would not get managed correctly when sharing a project in SourceSafe mode.
|
|
6517
|
Real Time DB
|
The GetXMLSettings functions of some basic interfaces would not return the XML code when exectue3d from the MoviconRunTime.exe module. The interfaces effected with this problem were:
DBVarObjCmdTarget
DBVariableCdTarget
OPCClientGroupObjCmdTarget
OPCClientItemObjCmdTarget
OPCClientObjCmdTarget
ScalingCmdTarget
|
|
8344
|
Real Time DB
|
When changing an element from one of two array variables sharing the same area and internal memory address, its value would not get updated in the other array.
|
|
4853
|
Real Time DB
|
When an element from the project was modified, the array variable when displayed in the Watch Window would not update. In particular, the value would not updated in each individual element displayed when expanding the array.
|
|
8333
|
Real Time DB
|
Movicon would go into error when stopping and restarting a project in design mode that contained a array type variable exchanged with the field.
|
|
8345
|
Real Time DB
|
Array types different from Bytes would not get handled properly in the Watch Window. Basically, when an element changed in an array type that was different from a byte, all the other elements would get overwritten in the Watch Window as well.
|
|
8516
|
Recipes Management
|
When the name of a column started with a number or contained spaces, the "Save" command would not insert the value in the record. This would usually happen using a database that supported these type of syntax.
|
|
8322
|
Screen Objects
|
The Combo-box object would not work properly when overlapped with a window which had its "Show Control Window" option enabled.
|
|
8382
|
Screen Objects
|
The Trend object's Print button would print the last page by mistake instead of the one currently displayed.
|
|
7684
|
Screen Objects
|
Setting a layout different to the one for default in a display window, such as the Alarm Window, TraceDB Window, etc., Movicon would change the layout back again on the next page load in design or runtime mode.
|
|
8218
|
Screen Objects
|
The configuration file of a Trend or Data Analysis object would not save correctly when the Trend area had been expanded.
|
|
8396
|
Screen Objects
|
The "Default Filter" and "Default Sort" properties from the Data Analysis object would have not effect when the "All" date range had been selected.
|
|
8567
|
Screen Objects
|
In certain cases clicking on the horizontal bar of a Display Window (Alarm Window, Log Window, etc.) Movicon would loose focus and objects could no longer be clicked on and the only way to restore situation was to click outside the Movicon window. This problem would occur only if the "Auto Column LayOut" property had been set in the display windows.
|
|
3312
|
Screen Objects
|
In certain cases the strobe command when executed in variable bits, "<Variable>.<NrBit>", would not return bit to zero after the time, defined as parameter, run out. This problem would only occur when the variable has a value different to the zero value.
|
|
8557
|
Screen Objects
|
When a print was executed in a Trend object using the appropriate button while Trend was in Run mode, the run/stop button would disable and would not reactivate unless screen was reloaded.
|
|
8433
|
Screen Objects
|
The Meter needle's position would not get recalculated when the minimum and maximum scale values changed.
|
|
8321
|
Screen Objects
|
When the "View Expanded List" option was enabled in the Alarm Window where alarms had not been associated with help strings, every time an alarm activated a second row would appear either blank or reporting a message of an already displayed alarm.
|
|
8562
|
Screen Objects
|
The GroupBox object would not align text correctly on more than one line.
|
|
8350
|
Screen Objects
|
The Alarm Banner object would not handle background colors correctly when the "Blink time" had been set to zero.
|
|
8338
|
Screen Objects
|
The Chart object would not work correctly if connected to array variable that were not in Byte.
|
|
6873
|
Screen Objects
|
When the "Recipe Manager" and "Scheduler Window" (Hour Selector) were displayed within an "Embedded Screen", the Drop-down list for selecting recipes, eventual schedulers and variables would not display in the plan list.
|
|
7504
|
Screen Objects
|
A Meter scale, in design time, would get redrawn with default values following an undo operation on screen. This was only a visual problem as the scale would reset with the right values when the screen was closed then opened again.
|
|
8432
|
Screen Objects
|
The "FocusCellText" function from the "GridWndCmdTarget" interface would not always update the cell that was being focused on in that moment but another one by mistake and would ignore following database update commands.
|
|
6614
|
User Interface
|
The Watch Window and Runtime Brain Windows 7 platform would not refresh correctly when launching the project in Runtime. In particular, some buttons would not display until passed over with the mouse.
|
|
8360
|
WebClient
|
In certain cases the number of Web Clients connected to Server would not decrease when a Web Client disconnected.
|
|
8529
|
WebClient
|
When a Web Client called a page requiring some time to load (i.e. a page containing a Grid object to be populated with a certain amount of data), this would regenerate timeouts that would cause the applet to make attempts to reconnect. In this attempt to connect phase a problem would occur when the TCP connection which had been opened by the applet for reconnecting would disconnect straight away leaving the Web Client still connected on the Server side.
|
|
8564
|
WebClient
|
In certain particular cases when a Web Client tried to connect to a network Server with the User management active, if the login message was sent repeatedly to the Server due to connection timeout, the Server would put the Web Client's IP into quarantine. Before attempting to connect again the Web Client had to wait quite a while until the IP address was released from quarantine (default 60 minutes).
|
|
8520
|
WinCE OS
|
Screen loading would noticeably decrease in performance when passing from version 11.0 to 11.2. This was caused by the new Static Alias management.
|
|
1784
|
WinCE OS
|
In certain cases Movicon CE would ask user to enter softkey even though already done so. This happened, for instance, when activating a new network card on the device.
|