This version also includes fixes to problems resolved in 11.0.0.1017 and 10.2.0.962 versions.
ID
|
TOPIC
|
PROBLEM SOLVED
|
3665
|
DOM (Document Object Model)
|
The "OnPreSymbolLoading" event added for drawings. This event is called before object is initialized, therefore before the "SymbolLoading" event and allows operations to be performed which otherwise could not by the fact that the object had already been initialized. For instance, a symbol's default structure or one of its elements can be changed.
|
3910
|
Screen Objects
|
A scheduler's configuration using the scheduler window would have problems when the variable names in the variable list (the "Variable" column) were subject to language change. In fact, the hour plan got saved with the variable name based on the language active at that moment, and not with the actual name of the variable in the project. This would stop the variable set from being executed.
|
1309
|
Design
|
When importing a wmf file and then creating a symbol, the symbol would show less defined and not exactly the same as the wmf image it originated from.
|
1984
|
Basic Scripts
|
Switching over to runtime mode from the design ambient would stop basic events in variables within drawings from being executed even when the variable values changed.
|
2694
|
Basic Scripts
|
Movicon would raise an error and close when executing a script that had created references to screen objects when the screen was no longer loaded in memory. this would happen using the "GetSynopticInterface" and "GetSubObject" functions for creating a "DrawCmdTarget" type variables within an external script resource. This error is now handled differently so that the script execution error appears without terminating the application.
|
4368
|
Design
|
The Cross Reference list would not show those variables which had been used in screen basic script code or in screen object basic script code.
|
4337
|
Report Management
|
The "Export Report" command would not work because the external process called by Movicon (ReportViewerNET.exe) would raise an error straight away.
|
4069
|
DOM (Document Object Model)
|
The "OnHelpAlarm" basic event of an alarm threshold would not get executed when the "Help" button was pressed within the alarm window with the selected alarm.
|
4316
|
Screen Objects
|
The "OnTextChanged" basic event would get handled for the grid object and scheduler window object in grid mode. As a consequence, basic script code could no longer be sued for carrying out controls on values entered in grids or scheduler window grids.
|
4257
|
Real Time DB
|
The Cross Reference List would not show variables that had been associated to alarms, event or data loggers, when directly associating them in the project's variable database.
|
4422
|
OPC Communication
|
The Movicon OPC Client XML DA was unable to connect to "unsignedbyte", "unsignedshort", "unsignedint" or "unsignedlong" type items.
|
4576
|
Real Time DB
|
Variable structure members' statistical data was not retentive. Thus when restarting the project their values would get initialized at zero.
|
4716
|
Report Management
|
The "View Synchronous" and "Print Synchronous" report category commands would not work generating a message using the devexpress report integrated within Movicon.
|
4748
|
Screen Objects
|
The "Dynamic Property Inspector" window would not work correctly with variables set in screen object "Dragging" group properties.
|
4648
|
OPC Communication
|
When a structure variable went into use, a task or a OPC group which was linked to a one of the structure's members would not go into use. This problem would occur in client-server projects when client connected the whole structure variable with the server.
Note: this problem has also been fixed in those communication drivers which implement the new 256 base classes or later versions.
|
4931
|
Screen Objects
|
A scheduler window would not preserve the color set for cell selection when updated after public symbols or style source container has been managed. These color options now work properly to allow user to choose whether to preserve or not this characteristic.
|
4917
|
DOM (Document Object Model)
|
The "AlarmWndCmdTarget" basic interface "OPC AE Server" method would freeze the Movicon application. This problem occurred when the name of the OPC AE Server was reset with a nothing string, when previously set in a valid OPC AE Server.
|
4849
|
Screen Objects
|
An editable display set for displaying statistical values of variables, would send Movicon into error when variable did not exist in the project.
|
4954
|
Design
|
Movicon would go into error and close a project after structure variables and structure prototypes had been copied from one project to a second project while both opened in the same workspace.
|
4859
|
Design
|
Taking a template from the library and inserting it on screen, the two "Enable Move" and "Enable Resize" options from the "Dragging" group properties would get reset to "false".
|
4880
|
Screen Objects
|
The grid object would not insert columns in the grid in the order they has been set suing the wizard.
|
4898
|
Design
|
The condition list used for filtering alarms based on their severity in an alarm window would show the wrong descriptions: "major" should have read as "major-equal" and "minor" should have read as "minor-equal".
|
4953
|
Real Time DB
|
A structure variable member's statistical values would not get zeroed when the day, week, month or year changed.
|
4761
|
Tools
|
The runtime user editor would not handle the "TimePassword" attribute correctly. As a consequence the password expire would not get handled correctly for runtime user is enabled with one.
|
4660
|
Screen Objects
|
The variable set as a combo box's ListBox list variable would not get handled by the following functions:
|
4662
|
Networking
|
A request for a variable trace comment did not get made in cases where the variable was linked to a network server. Now a comment request is also made in client stations and saved in the server's database.
|
4677
|
Recipes Management
|
A new "Always in use" option (default "true") has been added to the Recipe object. When setting this option to "false" the variables used in the recipe fields will not go into use when the recipe is initialized. As a consequence, these variables will only get counted on the license if the recipe activation command is invoked or for the time needed for transferring the recipe values to the field (by means of using the opc client or communication driver).
|
4749
|
Screen Objects
|
The variables used in drawing animation color thresholds, texts and bitmaps could not be replaced using the "Dynamic Property Inspector" window.
|
4707
|
WinCE OS
|
A file path or resource resolution would fail in Window CE. For instance, this problem would occur when opening a screen in parameterized mode when the parameter file resided in a project work folder.
|
4548
|
Design
|
The variable editor and string table's filter and order by operations did not support the Escape key. Now these operations can be aborted by using the "ESC" keyboard key.
|
4504
|
Design
|
The escape key with the string table opened in popup mode, would nevertheless associated the string selected in the control window.
|
380
|
Design
|
The name of the basic script, menu and accelerator screen resources only supported alphanumeric chars. As a consequence, in design mode, problem would arise with resource copy and paste operations in the "Project Explorer" window in cases where resources had been renamed externally to Movicon containing alphanumeric characters. Now it is possible to using all the characters consented by Windows in file names, such as: ! £ $ % & ( ) = ^ ' [ ] + @ # ° § ; , . - _
|
3213
|
Report Management
|
The "Export Report" command exported reports to the Movicon installation folder and not the project's "DLOGGERS" folder (or the one configured for the project's data loggers).
|
3911
|
Screen Objects
|
The scheduler window would not update names of variables set in the "Variable" column when the active language changed.
|
3653
|
Screen Objects
|
The buttons did not support multi-line texts when alignment type was set to "bottom" or center".
|
3531
|
Documentation
|
The online help incorrectly stated that an alarm could be set in more than one area using the ";" char.
|
3212
|
Report Management
|
Exporting a report in jpeg format with the tool "ReportViewerNET.exe" tool created an empty image.
|
1921
|
Design
|
When a symbol associated with an alarm got inserted on screen, all the variables, accept the one set as an alarm variable, were inserted as word types. In addition to this, if these variables had been added in the real time db with a different name and not their original one, their new name would not get set in the alarm's properties.
|
3223
|
Design
|
In the "View" menu, the "Symbols" option tick would become visible/invisible according to "Status Bar" status and not that of the "Symbols" toolbar's.
|
4068
|
DOM (Document Object Model)
|
"OnCommentAlarm" basic event of an alarm threshold would not get notified when an alarm comment was modified, for instance, when using the "LastComment" property from the "AlarmThresholdCmdTarget" interface.
|
4345
|
Design
|
The Tag browser" window had editable fields when editing was only consented by right clicking on the variable through a second popup window.
|
4489
|
Design
|
The "Ins" button from the keyboard, would not allow new string ids to be added when the table was opened in popup mode.
|
4605
|
Screen Objects
|
An editable display linked to a string type variable and with the "Prompt Pad" option, would open the alphanumeric Pad in without being able to insert an additional char. in respect to max. value originally set in the display's property.
|
4757
|
Alarm Management
|
It became impossible to find out the number of alarms ON and OFF. To remedy this, tow new system variable members have been added called: "NumActiveAlarmsON" e "NumActiveAlarmsOFF".
|
4780
|
Design
|
The "Create DB Table" command in a variable's Trace options showed an error in cases where the DB trace has been set for using the InMemoryDB.
|
4847
|
Design
|
The public symbols management would not preserve dynamic variables in an object list or combo box, even if the "Preserve Dynamics" property had been set.
|
4830
|
Real Time DB
|
The "Inverse" scaling option set directly in the variable would not get handled correctly.
|
4850
|
Screen Objects
|
The public symbol management would delete all the variable columns when updating a datalogger window object.
|
4973
|
Redudancy
|
In a redundant system when the primary reconnected to the secondary, not all the statistical information got recovered by the connecting variables with their 'Enable statistic Data" enabled.
|
4679
|
Design
|
Some vectorial image import commands in a screen have been fixed.
|
4884
|
Screen Objects
|
Data logger and recipe associations to Movicon objects which interface with databases have been improved. Beforehand, you could indistinctly associate recipes or data loggers in any object which used a database. Now, recipe type objects are filtered for those objects which work only with data loggers. The same goes for the data logger and recipe object drag and drops in screen objects.
|
5065
|
WinCE OS
|
The "capture and Print" command would not work in windows CE.
|
5177
|
WebClient
|
The Trend and Data Analysis print button partially remained visible in the Web Client, even though it could not be used.
|
5166
|
Redudancy
|
The comment would not get saved in a variable trace db if the variable had been modified in the secondary in a redundancy system.
|
5168
|
Screen Objects
|
The window type objects would not become invisible/visible according to the set access level in read.
|
5056
|
Screen Management
|
Selecting a screen object containing many elements would be very slow in opening with the "XML code Explorer" window open as well.
|
5016
|
Design
|
The cross reference list could not always find all variables used in scripts. This problem would arise when structure variables had also been used in script code.
|
4937
|
Screen Objects
|
The data logger window layout would not always be correct when displayed within a "Tab Group" object.
|
2099
|
WinCE OS
|
MaxLogEntries and MaxLogFiles values set different to those for default (100 e 10) in the MovXCE.ini file, would get ignored while creating System.log files and successive backups.
|
4528
|
Screen Objects
|
Square buttons would not always be correctly displayed and would show horizontal lines with colours different to the ones set in the buttons.
|
5050
|
Design
|
The "Replace Symbol" command would raise an "Error not specified" message.
|
5057
|
WinCE OS
|
The "Execute Synaspe" command would not work in Windows CE.
|
5054
|
Screen Objects
|
An alarm window would not preserve the color set for historical data when updated after public symbols or style source screens had been handled. Now this object has been provided with options to preserve these types of characteristics or not.
|
5001
|
Screen Objects
|
A Trend set for recording data on file always displayed the historical part when put in stop mode.
|
5169
|
Screen Objects
|
The minimum and maximum value formats in edit-box display error messages ware not correct when the variable happened to be integer type but had a format with a point in (i.e. "x.x").
|
5274
|
Design
|
Log files belonging to a project could not be read if containing unicode characters and the os was unicode type (i.e. Windows in Chinese).
|
4174
|
Real Time DB
|
The "General->FloattingPointPrecision" DWORD value has been added to the windows configuration registry (default = 0) which allows extra precision in converting numbers with floating points (float and double) in texts. The default "0" value means that standard precision equal to six figures will be used.
|
5087
|
Networking
|
The "Unknown Error" would appear when inserting two alarm windows both connected to a unavailable network server.
|
5305
|
Redudancy
|
The primary would display "Unknown error" error while synchronizing the Secondary. This problem would occur when the two projects where not the same (a condition that could have been avoided but now is managed correctly).
|
5289
|
Design
|
When Inserting a new variable in the "Tag Browser" window it would not show on the list if a filter had not been applied to the variables beforehand.
|
5342
|
Screen Objects
|
A pen's import window would open when double clicking on a button or in an area which should have not invoked this command.
|
5067
|
WinCE OS
|
Printing a screen capturing graphics with the "Capture and Print" command, the print window in process would also show. This problem occurred only when using this command in Windows CE.
|
1582
|
WebClient
|
The "Numeric Pad" command if used by WebClient would not take into account the set Minimum and Maximum limits allowing any value to be inserted. Now these set limits are managed in the command and are shown in the input window title which is opened by the Web client to edit values.
|
1911
|
Redudancy
|
In redundancy mode, modifications to recipes on the primary or secondary would only be updated in the primary project, and not in the secondary. The secondary project's database would only update following one of these conditions:
-
Stopping the primary project
-
Stopping the secondary project
-
A datalogger recording event
|
5226
|
Report Management
|
Displaying a report with a chart object, the chart would display without data.
|
5212
|
Screen Objects
|
The window objects predisposed for connecting to a network server, would show data that the user set for logging on to Server that should not have been revealed according to their access level mask. This would happen only if a default user had been set in the server application for clients that gained access with anonymous authentication.
|
5246
|
Setup
|
The setup did not warn the user that operating system did not have Microsoft ActiveSyn installed and therefore the Movicon component for Windows CE would not get installed for default.
|
4049
|
Design
|
The "Refactoring Explorer" window showed an error when selecting the "Redundancy" resource in the project explorer window.
|
4527
|
Design
|
When using in design mode a screen tab in the MDI bar would disappear, when using the open command of a screen already opened. It would only reappear when modifying the Movicon workspace size.
|
4550
|
Design
|
The "Find" command wouldn't work correctly is used in the project variable editor.
|
4822
|
Screen Objects
|
The transparency level in the public symbol management would not get copied to the destination symbol by the source symbol.
|
5322
|
Screen Objects
|
A Trend recording on file function would have problems if the file name, to be used for recording, was not specified.
|
5303
|
OPC Communication
|
The "OPCXMLDAClient.log" log file was not bound to the "Trace" DWORD value equal to "1", in the windows "General" configuration registry for the Movicon application. As a consequence a project that connected to an OPC XML DA Server would keeping creating and recording in this file occupying using up unnecessary space on disk.
|
5369
|
Setup
|
The product's help file would not get installed when modifying components from a previous installation which had not been needed.
|
5461
|
Screen Objects
|
When an external configuration file as loaded, the column positions and sizes in its layout were incorrect.
|
5359
|
Screen Objects
|
Contents from some work windows in a project would get updated in synchro mode with the user interface, even when not displayed. As a consequence this would slow down object selecting, above all on screen. The windows experiencing this problem were the XML code explorer, the script explorer and the IL code explorer windows.
|
5344
|
Screen Objects
|
Focus stayed on a grid object even to moved to another object. As a consequence, the selected cell would also move in the grid object when using keyboard arrow keys with focus on another object. This same problem also happened with grids used in the "Scheduler Window" object.
|
4650
|
Networking
|
Using the child project techniques for creating a client project, the variables which connected to the server would not get removed when no longer in use in the client.
|
4014
|
Design
|
Software licenses could not us used with the Windows VISTA operating system.
|
5412
|
Screen Objects
|
The item in a drop-down list became selectable with the mouse even when drop-down list was not visible. This problem would show in the "Combo Box" and "Scheduler window" objects when set to display the combo box for selecting schedulers only. This problem starting happening with the build 1017.
|
5437
|
Screen Objects
|
Closing a screen opened in modal mode would raise an error in the Movicon application if being run on a Tablet-PC with Windows VISTA.
|
5447
|
Screen Management
|
The INSERT or UPDATE command of a grid object failed if the table's name contained a space.
|
3283
|
Setup
|
When Movicon launched an external executable in Windows Vista with the UAC enabled, the Windows' PCA (Program Compatibility Assistance) would intervene impeding the tool's execution. The subsequent generated message would be misleading stating that file could not be found when actually this was not the case.
|
4391
|
WebClient
|
Publishing a data logger as a data web page with the appropriate command, problems would arise using the selection controls to filter data when not using a Internet Explorer. Data could be selected but the last piece of data would not get displayed in the control.
|