|
ID
|
TOPIC
|
PROBLEM SOLVED
|
|
7116
|
Alarm Management
|
Inserting a basic script expression in the alarms, the persistent file (.alr) would not get created due to the string end character inserted by the expression manager.
|
|
5570
|
Alarm Management
|
The acoustic warning would not sound for alarms in 64 bit operating systems. The audio card is now used for sounding alarm occurrences.
|
|
6924
|
Basic Scripts
|
The Display object's DisplayEditCmdTarget" interface's "FormatData" property settings would not get applied.
|
|
6741
|
Basic Scripts
|
The On[Variable]Changed event would get suspended and would not reenter into action after a certain time had elapsed.
|
|
1460
|
Child Projects
|
A control used in child project screen, would use the parent project's homonymous variable when the child project screen was displayed as an embedded screen within a parent project screen. Incompatibility: the variable in the context in which the resource is found is now used, which beforehand was searched for in the parent project.
|
|
7072
|
Child Projects
|
A child project resource which used a parent project variable would not receive notification when this variable changed. This problem concerned those resources that were initialized only when the variable changed (i.e. object events). When a resource of this type used a parent project variable, the child project would not get notified of any variable value changes if they happened towards the end of the project startup phase.
|
|
6878
|
Child Projects
|
When a child project was set for connecting to a network Server, all the objects that had to recover the value from the variable's "Default Format" field, were unable to. As a consequence, the controls used a null format.
|
|
6631
|
Design
|
Files inherent to the Communication Driver would not get managed correctly when inserting a project in the Movicon Source Safe.
|
|
6943
|
Design
|
Setting a textual report command in the Report commands and then adding the name of the template file in the "Textual Report : Layout File" field, when reopening the command the same file name would appear in the "Textual Report: Destination file" field.
|
|
7115
|
Design
|
The "Apply New Name" and "Apply Renamed Variables and Resources" command would not zero the alarm, data logger and "_c" files.
|
|
7099
|
Design
|
The "Exclusive Write Access" properties help string was not completely correct.
|
|
6842
|
Design
|
A symbol's "Regroup" command would not work correctly when the symbol's components had been set with a Command List in their "Commands on Click" execution property.
|
|
2561
|
Design
|
The basic script expression editor would not validate an expression when considered invalid, for instance, when using the "/" operator for dividing (division by zero in design mode is generated due to fact that variables are not initialized). Now, even if expression is not considered as valid because it cannot be resolved in design mode, a request to confirm or not is nevertheless shown.
|
|
6420
|
Design
|
The Alarm window's "Filter by Area" property would not display the list of areas until the project's alarm list was expanded.
|
|
6117
|
Design
|
the asterisks would not show in some resources, such as the Basic Script, editor window's tab when the resource was modified.
|
|
977
|
Design
|
The 'Embedded Screen' object would show the associated screen applying the zoom. This behaviour showed while the "Embedded Screen" object was being loaded with its own embedded screen, applied with a zoom factor, was still opened in editing mode.
|
|
4795
|
Design
|
If the Movicon color selection window was open on screen, it would remain open when a window from another process was selected.
|
|
3310
|
Design
|
The 'Find' button from the main Movicon 'Tool Bar' would result disables no what context it was found in.
|
|
6624
|
Design
|
Copying and pasting a certain number of selected resources at the same time, the name of the last resource selected would be used as the reference name instead of the last selected resource's name. Therefore all newly created resources would use the first selected resource's name.
|
|
6625
|
Design
|
In certain conditions in design mode the screen navigation bar would not display in screens requiring its use.
|
|
6845
|
Design
|
The "Check for Updates" command from the Movicon Symbol Library or Communication Drivers was case sensitive.
|
|
7037
|
Design
|
In certain cases when modifying a variable a "beep" would sound, after which it became impossible to modify the variable's address.
|
|
6219
|
Design
|
Screen cross references would not always work properly.
|
|
6740
|
Design
|
After having inserted a Dundas meter on screen, when modifying this object Movicon would not notice that object had been modified and would not check project for saving.
|
|
3206
|
Design
|
Dragging a variable onto a TraceDB window, an inquiry was made asking which animation option should be set instead of associating the variable directly to the window's "Tag Table".
|
|
6680
|
Design
|
When a screen or basic script resource did not have a name in unicode chars, the "Separate thread (Open Safe)" or "Spawn in separate thread (Run Safe)" failed to work generating this message in the output window:
The file 'C:\DOCUME~1\Daniele\IMPOST~1\Temp\TFR10A.tmp' has been saved NOT with Unicode encoding while was containing Unicode text
|
|
3121
|
Design
|
After performing an "Undo" operation while editing a screen in development mode, all the screen objects associated to an invisible level became visible, even though all those levels that were disabled before the "Undo" operation remained disabled in the toolbar.
|
|
3954
|
Design
|
Symbols of variables with or without sign would show inverted in the Tag Browser window.
|
|
3523
|
Design
|
The "Topic" parameter of a command from the "Help" category did not have a button for opening the string table's modal window used for easy String ID selecting.
|
|
6653
|
Design
|
The variable retentivity files (.var) and the persistent alarm files (.alr) were also saved in ANSI even though the project had been set in Unicode.
|
|
3478
|
Design
|
Fields relating to the report would remain displayed when IMDB Datalogger or Recipe properties were displayed.
|
|
7057
|
Design
|
Opening the Symbol Library and clicking on the "Toolbar Options" menu, a menu would appear containing an item with <without title> written.
|
|
7053
|
Design
|
Accessing a screen's "Drawing object" list from the Project Explorer window and selecting a symbol contained within another symbol by ungrouping it using the command from the Symbol menu bar, Movicon would raise an error.
|
|
7114
|
Design
|
When a basic script expression was used outside a screen object, for example in an alarm or DataLogger, the variable's "Apply new command" command would leave the old name without applying the new one in the expression.
|
|
3351
|
Design
|
Screen background color filling would not fill completely using the "horizontal" gradient leaving a space colored with the screen's background color on the right hand side.
|
|
3292
|
Design
|
The Open Cross Reference command would not appear in both the main toolbar and View menu.
|
|
5044
|
Design
|
The "Tag Browser" window would display variables in the wrong group. This problem would arise in projects that had complex group structures where some of the variables' names coincided with some group names.
|
|
6034
|
Design
|
A child project variable would get inserted on the parent project's variable list. This would happen when a child project variable was modified using the Tab Browser window. In this case the modification would also add the variable to the parent project's list.
|
|
6584
|
Design
|
When a project had a number of child projects embedded within each other, each with groups of variables using the same name, not all these variables would get displayed in the Tag Browser window.
|
|
3522
|
Design
|
In a "Report-Recipe" command, corresponding to the "Data Logger-Recipe" parameter, the drop-down list showing all the DataLoggers or Recipes in the project would not appear to facilitate selecting procedures.
|
|
3124
|
Design
|
The control for accepting a new string ID in the "String Table" was not case sensitive. For example, after having inserted an 'A' id, the "a" id would not get accepted.
|
|
7237
|
Design
|
The hatched area indicating area occupied by the Screen Navigation Bar in design mode would not get drawn with right proportions when applying the zoom to the screen.
|
|
7204
|
Design
|
The "Project Explorer" window would sometimes remain on display when running project from the development environment.
|
|
2572
|
Design
|
When exiting the project, modifications to resources would be confirmed (Check-In) automatically in Source Safe. Registry keys have now been added for modifying this feature.
|
|
6738
|
Design
|
The user interface would freeze when selecting a variable within the Movicon workspace and modifying the a structure prototype member type using the XML Code Explorer window.
|
|
2571
|
Design
|
When opening the "Variable List Window", the automatic check-out (extract...) would not execute as with other editing window for other resources.
|
|
2573
|
Design
|
The "Source Control" item would not appear on the menu which showed right mouse clicking on the "Navigation" resource. This only happened for this resource.
|
|
181
|
Design
|
when selecting a parent project resource or variable in a child project property, the "..\" prefix would not be added to the name of resource to indicate that it referred to the parent project.
|
|
3071
|
Design
|
When copying-pasting a screen, the background image would not show in the screen when copied: it would only show when the project was closed and the reopened in development mode.
|
|
4831
|
Design
|
When inserting a symbol from the library that used variables and then selecting a variable field from the Dynamic Property Inspector window followed by pressing the OK button, the selected variable would not get added with an increasing index if one already existed in the RealTimeDB.
|
|
4514
|
Design
|
When a Scheduler Window object slightly went outside the screen, it would start flickering.
|
|
3499
|
Design
|
The script editor window and the "Script Explorer" window support the "Open #Uses" command. This command adds little numbered tags, "2, 3, etc", for each script module that has been included with the "'#Uses" command in the main "1" module. Passing over to one of these modules, the modifications carried out would not be retained when the editor window was closed. Now the secondary modules are opened in read only and therefore cannot be modified.
|
|
6946
|
Design
|
Symbols inserted from the Symbol Library would not get managed properly when changing Movicon versions.
|
|
3467
|
Design
|
Trend and DataAnalysis objects would start flickering when slightly going outside the screen boundaries.
|
|
6506
|
Design
|
The symbols in the Symbols Library would not get drawn when using the Antialiasing.
|
|
569
|
Design
|
Exploring a menu with the "Project Explorer" window, the menu and popup items were shown in alphabetical order and not in the programmed order.
|
|
6669
|
Design
|
Movicon would not load the ".uxp" file containing the user passwords when the project was run for the second time.
|
|
6175
|
Design
|
Memory leaked when using the "Tag Browser" window when called from the project properties window, then closed followed by closing the project as well without waiting for the property window to complete confirmation procedures.
|
|
7006
|
Design
|
When Drag&Dropping a variable onto an object, such as the rectangle, some animation options appeared missing from the list for associating the variable which included:
Transparency
Text - Display Value
Images Animation
In addition, when you now Drag&Drop a variable onto a Trace or Data Analysis object while pressing down the CTRL key, the pen will be added to those already existing. Otherwise, if you don't use the CTRL key, all the existing pens will get deleted.
|
|
2863
|
Design
|
While creating a project using a Wizard within Movicon, any DataLogger that was created would get set with an age higher to those of the "MaxDaysAgeHistoric" and "MaxCacheBeforeFlush" constraints. However this would not happen to other DataLoggers added afterwards.
|
|
5707
|
DOM (Document Object Model)
|
The "NetworkBackupServerName" property for reading/setting the Backup Network Server had not been included in the AlarmWndCmdTarget, DLRWndCmdTarget, HisLogWndCmdTarget, TraceDBWndCmdTarget, HourSelectorCmdTarget and RecipeWndCmdTarget interfaces.
|
|
6518
|
DOM (Document Object Model)
|
The "DeleteRow" method from the "GridWndCmdTarget" interface would not delete the row if the cell had not been selected with the mouse beforehand.
|
|
6257
|
Networking
|
Enabling the Audit Trail of a structure variable and modifying the variable's members on the client side would record values as byte array types in the database.
|
|
1475
|
Networking
|
Executing a script from a remote debug session would not execute the script on the Server. This malfunction would only show in the PowerHMI version.
|
|
3831
|
ODBC
|
The "ODBC Real Time I/O Link" feature would first execute an INSERT and if the INSERT failed, it would execute an UPDATE. Now these two commands are execute in reverse sequence.
|
|
7315
|
OPC Communication
|
Movicon was unable to communicate with the OPC XML DA Servers which used the "ItemPath" attribute to identify the item.
|
|
7142
|
PowerHMI
|
Problems with the Chinese language in the PowerHMI version.
|
|
6841
|
PowerHMI
|
Comments on Alarm ACKs could be entered even though not supported by PowerHMI.
|
|
3357
|
Real Time DB
|
When defining two variables with the same Internal Address in the same shared area and then using them both in different basic expressions, when one of the two variable passed from the InUse to the Not Inuse state, the expression in the other variable would also stop being executed.
|
|
7211
|
Real Time DB
|
In very particular conditions Movicon would raise an error running a project with the statistics enabled in structure variables with enabled Intellisense.
|
|
7014
|
Real Time DB
|
If the two GetMemberObjectFromName and GetMemberObjectFromIndex functions from the DBVarObjCmdTarget interface were executed within the dropping code OnVariableCreated event, a nothing object would be returned.
|
|
7176
|
Real Time DB
|
A basic expression that used part of a text already existing in another expression would not get valuated in runtime. For instance, one of the two expressions below would not have been resolved:
1) 1 + VAR00001 + 1
2) VAR00001 + 1
|
|
7012
|
Real Time DB
|
When changing the name of one of the members belonging to a structure prototpe, the member order would change by moving the changed member to the end of the list.
|
|
6759
|
Real Time DB
|
The "SetTimeStamp" function from the "DBVarObjCmdTarget" interface would not work for variables in shared areas.
|
|
5965
|
Recipes Management
|
While putting a project into run mode the following misleading message would show in the output window:
Cannot find the variable '' for the DataLogger/Recipe 'Recipe' Data Logger/Recipe
'Recipe' failed to initialize
In reality the recipe actually worked ok.
|
|
6903
|
Report Management
|
The follow ODBC message would show when executing the a XtraReport "Export" command in Windows 2008 64bit Server:
Error when trying to populate the datasource. The following exception was thrown: ERROR [IM002] [Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified
|
|
6995
|
Report Management
|
The ReportViewerNET tool, used from command line or invoked by Movicon with the appropriated commands ("View report", etc), could not retrieve the ODBC DSN connection if running in a 64 Bit Operating System.
|
|
3914
|
Scaling Resource
|
The Normalizers would not work correctly when using 'integer' variables in normalizing. this behaviour would happen due to rounding off the scaled result: Movicon considered the rounded off value in the scaled integer value, as a change to its value, a bilateral scaling effect, perceived as feedback to modify the source value of the raw variable.
|
|
6804
|
Screen Management
|
When screens were inserted in nested folders problems would start happening:
1) An Embedded Screen inserted in an nested folder would not manage the "Embedded Tag Screen" properly
2) The "Open Next" and "Open Previous" page change commands would not work with screens inserted in nested folders.
|
|
7046
|
Screen Management
|
When enabling the "Add Back Button" or "Add Back to Startup Button" property in the Screen Navigation resource, the navigation bar would also appear in screens had hadn't been inserted in the resource and, above all, in screens opened as Modules or Frames.
|
|
6970
|
Screen Management
|
When closing a screen opened in a separate thread, the last screen loaded or the startup screen would not re-open.
|
|
803
|
Screen Objects
|
When enabling the "Spawn thread execution" property and inserting a Chart object on screen, an error message referring to the "DrawChart.cpp" file would show when starting up Movicon in simulation mode. The 'Chart' object no longer appears on screen and the following message appears in the output window:
(Failed to create chart. Make sure the object isn't inside a synoptic with the separate thread option).
|
|
6760
|
Screen Objects
|
When the "FitInWindows" property from the "SynopticCmdTarget" interface was modified in runtime, it would resize screen without having any effect on the screen objects.
|
|
6551
|
Screen Objects
|
Instead of rotating the string as a whole, each object's text character would rotate singularly.
Incompatibility:
Text rotation will be treated with the new methodology for imported projects saved with previous versions.
|
|
1716
|
Screen Objects
|
Associating a Visibility Level to objects contained in an Embedded Screens would not change their visibility when the container screen's Layer Variable changed. The screen had to be reloaded in memory to update the objects' visualization in the Embedded Screen.
|
|
6809
|
Screen Objects
|
The 'Enable Var.' and 'Status Var.' properties would always be hidden.
|
|
6794
|
Screen Objects
|
Movicon would raise an error in runtime when more than one Alarm Banner object had been inserted on one screen when the project's Heap memory management had also been enabled.
|
|
6564
|
Screen Objects
|
Problems would occur with public symbol heredities when using Embedded Screen objects. Now the objects in Embedded Screen are updated using the public screen set in the screen containing them. However, if no public screen has been set, the one set in the screen containing the Embedded Screen will be used instead.
|
|
7255
|
Screen Objects
|
The "DataLogger/Recipe" window could not retrieve a recipe from a Network Server.
|
|
3028
|
Screen Objects
|
Local variables of a screen contained in a "Tab Group" object or "Embedded Screen" object would not show because they were searched for in the "Tab Group" or "Embedded Screen" object's container screens.
|
|
6732
|
Screen Objects
|
A variable's "Increase" and "Decrease" commands would change the variables average statistic value even though it had already reached one of the set limits. For example, once the set maximum value had been reached, attempts to increase the variable further would only increase its average statistic value while keeping its actual value unchanged.
|
|
7056
|
Screen Objects
|
An object's border would not draw correctly with the Antialiasing activated.
|
|
7157
|
Screen Objects
|
When an Embedded Screen object displaying a child project screen was inserted within a parent project screen, the Embedded Screen's String ID would not get resolved. The same problem also happened with object Images and Configuration files.
|
|
7196
|
Screen Objects
|
The "List Box" object would not draw the item list correctly if the screen had not been enabled with the 'Fit in Window' option.
|
|
7251
|
Screen Objects
|
Display objects would not save current column settings in the external configuration file.
|
|
353
|
Screen Objects
|
The "Tab Group" and "Embedded Screen" objects would not adapt to screen if already in memory. Therefore, the embedded screen contents would display over the embedded screen's borders instead of staying inside.
|
|
7171
|
Screen Objects
|
Opening a screen containing the Alarm Banner, the object would quickly scroll all the alarms in the system instead of just showing the last one.
|
|
5101
|
Screen Objects
|
A drawing configured to show only in a certain level, would not show when this level activated when drawing was within a symbol.
|
|
7010
|
Screen Objects
|
Movicon would raise an error changing page when the Trend was put into Pause mode and used Visibility Animation to hide it.
|
|
7034
|
Screen Objects
|
The Data analysis, Trend or screen print would not work if the Antialiasing had been enabled.
|
|
7140
|
Screen Objects
|
A Data Logger window object would always show all the associated Data Logger columns.
|
|
6611
|
Screen Objects
|
The object gradual filling would not work if the Antialiasing had been enabled.
|
|
6921
|
Screen Objects
|
If the "Area Filter" property had been set in the Alarm Window object of a project containing a large number of alarms (i.e. 1000 and more), the active alarm list would take a few seconds longer to populate when opening the Alarm window to view.
|
|
6945
|
Screen Objects
|
The 'Radio button' object would not accept empty strings as the first list item in the "Object Title" property. In fact if the first Item (the object's Title text) was an empty string, all the other option items would not get shown.
|
|
6862
|
Screen Objects
|
Screens used for Numeric or Alphnumeric pads, Get Password and Expired Password dialogs would open up in the position where mouse was clicked on and not in the centre of the screen.
|
|
4889
|
Screen Objects
|
The Display window's "Choose Field" window would not close automatically if exiting from the screen or saving the project.
|
|
1320
|
Screen Objects
|
Columns set in a "DataLogger/Recipe" window would disappear after a change language. Incompatibility: 1) Opening a project saved with a previous version might not show all the columns until project is saved again. 2) The "DataLogger/Recipe" window does not have reverse or downwards compatibility if saved with current version.
|
|
6817
|
Screen Objects
|
Some objects (Imbedded Screen, TraceDB window, Recipe Manager window) would not show all variables when public symbols.
|
|
6818
|
Screen Objects
|
The 'IP Telecamera Refresh Time Variable' property would display based on the "Preserved Commands" property settings when the symbol was made public. When the "Preserve Variables" property was enabled, the 'IP Telecamera Refresh Time Variable' property would only show if the "Preserve Commands" property had been enabled as well.
|
|
6823
|
Screen Objects
|
An object's Dynamic Image animations would send Movicon in error if the list of images was empty.
|
|
6982
|
Screen Objects
|
When the antialiasing was active, the arrows and dotted lines would not be drawn correctly.
|
|
6951
|
Screen Objects
|
The Recipe Manager object's "Execution > Project" execution property would not be retained after being set.
|
|
6947
|
Screen Objects
|
Using a scheduler Window with the "Variable" column enabled for allowing variable modification in runtime, the variable selection list remained empty if a child project had been linked in the project.
|
|
7104
|
Screen Objects
|
The dynamic tooltip would ignore the format of a variable value. The dynamic format now shows the value with the format set in variable and not in any control.
|
|
6896
|
Screen Objects
|
Switching to runtime mode and back again into development mode the text displayed by the IP Camera viewer object was the last text that was displayed in runtime.
|
|
6694
|
Screen Objects
|
It became impossible to change the measure value text color making values difficult to read when object had a dark background color.
|
|
6937
|
Screen Objects
|
Locked symbols could nevertheless be modified when selecting them through the Project Explorer Window.
|
|
6992
|
Screen Objects
|
The "Samples" property from the "TrendCmdTarget" interface could not be set with a value superior to 10000. This value can be exceeded by the Data Analysis object but not the Trend object.
|
|
7152
|
Screen Objects
|
A command set to execute upon mouse button release an object would not get executed if the object was a symbol component and the mouse moved before button was released.
|
|
6984
|
Screen Objects
|
If the alphanumeric pad for inserting passwords opened for default or in custom mode when using the custom password dialog pads, would permit passwords entries without substituting password with astericks.
|
|
6948
|
Screen Objects
|
An error would generate when inserting the start time in the Scheduler Window object in grid mode even though time was correct. This would happen if the end time was entered first when both the start and end times were the same.
|
|
6915
|
Screen Objects
|
Prints activated with a screen "Print" command would not print all the screen's objects (for instance, 3D buttons, Dundas meters etc.).
|
|
6902
|
Screen Objects
|
A problem would occur in the Scheduler window overlapping graphics when setting button alignments to an option other than 'bottom' with the 'Scheduler Selection comboBox', 'Add Scheduler Button' or Remove Scheduler Button' enabled as well.
|
|
7209
|
Tools
|
The "HisLogUpdate.exe" tool would raise an error at project startup when the project being run had been set a link to a missing child project.
|
|
7235
|
Tools
|
Importing variables with the "Csv Tag Importer/Exporter " pool would fail in certain conditions raising the "The read row is too long!" error when too many variables were involved.
|
|
6672
|
Tools
|
Problems with reading the runtime user's ".rtuser" file when reading when project had been set as Unicode or Crypted.
|
|
7169
|
User Interface
|
When changing document (screen, basic script, etc.) in the Movicon workspace by clicking the mdi tab, the resource that opened would close straight afterwards. This would happen when clicking on the same position where the 'x' to close tab appeared when opened.
|
|
7268
|
WebClient
|
When connecting different WebClient sessions using PCs with Windows 2003 Server OS, the Movcion Server project's instance would suddenly close without giving an error.
|
|
2997
|
WinCE OS
|
In systems with WinCE some system string concerning the Numeric and Alphanumeric pads would not substitute correctly according to the string table. The Sting IDs in question were:
_CANCEL_PADTEXT_
_DELETE_PADTEXT_
_OK_PADTEXT_
_CAPSLOCK_PADTEXT_
|