ID
|
TOPIC
|
PROBLEM SOLVED
|
3306
|
Menu Resources
|
A potential memory leak was detected during resource menu activation (non popup). Memory would leak when loading different screens where each one activated its own menu.
|
3294
|
Design
|
The "Undo" command would sent the Movicon application into error, if used for restoring a name of a resource group folder.
|
3325
|
WinCE OS
|
The MovXCE application would go into error freeze, when loading a data logger window set for showing a recipe resulted empty at that moment. This problem would only show if the recipe had been set to save data towards a SQL Server CE 2.0 database.
|
3328
|
Screen Objects
|
Opting to move one end of a synapse connector would generated an error in the Movicon application. This error would show if the connector's end was set in a point that didn't have a synapse and the properties window was open on screen.
|
3366
|
Design
|
There was a little GDI and User object consumption starting and stopping projects from the development environment. This problem happened only with certain window settings in the Movicon workspace.
|
3384
|
Screen Management
|
Opening a screen in another frame (Open frame (multi-monitor)) verified the consumption of USER objects. The consumption was quantifiable in '6' USER objects each time the screen was opened and closed. As a consequence it took longer to change pages which would only restore when restarting the project.
|
2475
|
Menu Resources
|
When users logged off a different menu and accelerator to the one set in the opened screen would get loaded.
|
2722
|
Screen Objects
|
Some objects would not be visible when the status variable was "uncertain" or "not connected". These objects now show using only the styles independently from the "bad", "uncertain" and "not connected" qualities.
|
2795
|
Users Management
|
On User logoff, or setting an "UserCmdTarget" object to "Nothing", the application would generate an error and close. This would only happen when the logged on user, or user referenced by using a basic script, while logging off were updated with new properties. For instance, when the user properties were modified with the runtime user editor.
|
2779
|
Networking
|
Some client variables would not reconnect when the server went into timeout. This situation would only happen when a basic scripted was executed at the project startup which put a least one variable into use, and if this variable tried to connect to the main server and a backup server without having access to the variable on the server.
|
2780
|
Networking
|
In a project with at least one variable set for connecting to a main server and a backup server, the CPU would get occupied up to 100% when there was no connection with the domain server and with the backup server.
|
3221
|
DOM (Document Object Model)
|
The "NumericEntry" and "AlphaNumericEntry" functions would send the Movicon application into error when used in a basic script resource. This error was reproducible only when the numeric and alphanumeric pad has been customized using a screen. In this case the Movicon application would go into error and close when the numeric or alphanumeric pad commands were used.
|
3226
|
WinCE OS
|
When the "Grid" object shared the same data logger connection, the datalogger's reset command followed by the Grid's refresh command would send the MovXCE application into error.
|
3149
|
Design
|
The Movicon application would go into error closing a project after an "Undo" operation had be preformed in the project explorer window. This problem would happen when the "Undo" operation was used in connection to inserting a variable group into the variable list.
|
3082
|
Networking
|
The alarm window used for connecting to the network server would display alarms with times with an hour more than the actual time in the "Time ON", "Time OFF", "Time ACK Time" and "Time Reset" columns.
|
3061
|
Design
|
The Movicon application would go into error when an "Undo" operation was performed in the project explorer window. This would only happen when the "Undo" was used in a screen with its object list opened in the project explorer window.
|
3052
|
Networking
|
A network client would freeze its user interface in cases displayed pages with a Trend that was set to connection to a network server in time or when the Trend window was refreshed continuously.
|
3053
|
Networking
|
The application would go into error and close when an object was set to connect to a network server. This would happen when notifications arrived for that object when the screen had already been unloaded from memory. This problem would happen with all those objects predisposed for obtaining historical data from network servers such as the Trend.
|
3043
|
Design
|
The "Save" command from the "Other windows...." window opened using the "Window" menu would put Movicon into exception. This command now disables automatically when not needed.
|
2826
|
Basic Scripts
|
When a basic script was loaded into memory, not all the variables would go into use. These were those which had been inserted in the code after a function from any one of the Movicon basic interfaces.
|
2857
|
Tools
|
When selecting the "New...." command from the "File" menu, the folders in the "Wizard" folder would also display in addition to the wizard plugins for generating new projects. Now only the ".movwiz" files display as is correct.
|
2873
|
Users Management
|
Resources became unable to execute write commands of variables if these variables had write access levels different to "0000" and when users did not have compatible access levels for that object.
This problem happened with the following resources:
-
Event Objects
-
Scheduler Objects
-
Basic Scripts
-
Recipes
-
Scaling Objects
|
2913
|
Networking
|
A network Client project would use a lot of memory in low performing devices/computers. This would mostly happen when using WinCE devices with slow CPUs.
|
2889
|
Comm.Drivers
|
When a driver task was connected to a child project variable, with the "<ChildProject>\<VariableName>" annotation, the driver would not receive any notification on whether the child project variable had changed value. Therefore, when the task was "Input/Output" type it would work as an input task only.
|
1306
|
Networking
|
Opening non startable child project screens, all the variables used in the screen would get reconnected to the backup server even when the main server was still active.
|
1286
|
Screen Objects
|
Movicon would go into error and close when unable to initialize an ActiveX. In short, the Active X would not initialize because it had not been installed in the operating system. Once the ActiveX had been installed, everything went back to normal. This problem would happen in all those points in which ActiveX is supported.
|
1287
|
OPC Communication
|
When variables were connected to a OPC Server in cases where items had been inserted into different OPC groups within the project, after terminating the OPC Server, Movicon would restart the OPC Server when timeout expired re-creating the only the first group on the list. This would cause the "The OPC DA Server .Softing.OPCToolboxDemo_ServerDA.1 (Group GroupName) is no longer available" error to be repeatedly entered on the OPC Client log.
|
1117
|
IMDB (In Memory DB)
|
When setting the option for recording a variable "timestamp" for a datalogger column ("Add Timestamp Column"), the recording would fail generating this error: "Syntax Error: Column not found in catalog" when using the IMDB.
|
1009
|
Child Projects
|
Modifications carried out in a child project's resource would not get saved with the "Save" command. This problem would show when a child project resource was open in edit mode, and then changed work context and edited a parent project resource. As a consequence the Movicon.exe process would remain pending when stopping.
|
1087
|
User Interface
|
The accented speech chars would block the Movicon user interface. Now Movicon uses the SAPI 5.1 which has solved this problem.
|
844
|
Screen Objects
|
When a variable ("Push Value Variable) in the chart object for updating data and this variable was associated to the chart curve was not array type, the number of points would not get managed correctly making it impossible to add the last curve point in the chart.
|
981
|
Screen Objects
|
The Grid object's "Save" command would set to null some of the record fields involved in the modification being applied.
|
984
|
Screen Objects
|
The Grid object's 'Delete' command would fail with an error caused by an incorrect syntax in the DELETE query sent to the database. This problem would show when a cell, of the record to be deleted, had a "null" value.
|
916
|
Basic Scripts
|
WORD tye variables (without sign) or DWORD (without sign) would cause an overflow error when used in Basic Scripts. This would happen when the variable used in the script exceeded the INT value due to the fact that the basic engine does not manage variables without sign. To avoid this problem a WORD type variable is now passed to the basic as Long type and a DWORD variable is created in the "Hauge_" basic which means "64 bit integer value" in the WinWrap.
As regards to the WinCE ambience, WORD variables can be managed but DWORD cannot (when exceeding the value of a Long variable), due to the fact that WinCE does not support "VT_I8" data.
|
906
|
Networking
|
A variable would be late in updating on the client when connected to a structure variable.
|
1517
|
Schedulers Resource
|
When modifying a scheduler object's scheduling Type property, would make the scheduler 'Commands ON' work incorrectly. This problem was linked to the fact that modifications to the scheduling Type property, did not delete the persisting ".shp" file. As a consequence the persistence file contained invalid information for the new scheduler type.
|
1527
|
IL Logic
|
Movicon would generate an exception closing a project that had previously been run and the stopped in development mode. This problem happened in conditions where variables in two different child projects were used in the project's IL logic and a page from one of these two child projects was loaded at startup.
|
1528
|
Child Projects
|
A project would try to synchronize with the primary, even when not set as a secondary project. This would happen when the project had a non-startable child project set as a secondary project.
|
1328
|
Real Time DB
|
Enabling a variable's "Real Time DBMS " property would window for inserting comments would get called at each variable read refresh, even when it hadn't been changed.
|
1847
|
WinCE OS
|
The "NumericEntry" and "AlphaNumericEntry" functions from the "UIInterface" basic interface opened the numeric and alphanumeric pad in the background in repest to the Movicon CE application. This problem was only reproducible when one of the two basic script functions was used within a basic script resource.
|
1876
|
WinCE OS
|
The decimal mode would not activate on a variable's "Append Values" command if the comma char was set as a decimal point in international settings.
|
1862
|
Networking
|
The "Alarm Window", "Historical Log Window", "traceDB Window" and "Trend" control would not support date and time conversions of the connected web client user's local time. When a web client user now connects to a server, the web client page shows the local time and date of the client and not of the server.
|
1955
|
Setup
|
Registry keys relating to documents (Movicon.Document) are now created in Vista as well.
|
1922
|
Design
|
It became impossible to enclose variable names between "#" chars in the alarm object's basic script and then add the alarm to the library. When trying to associate that alarm to one of the library's symbols, Movicon would raise an error and close.
|
1878
|
IMDB (In Memory DB)
|
A variable's trace table information would get lost when restarting the application. This problem only happened when using the IMDB recording engine. Now information is no longer lost and can be retrieved by using the TraceDB window only when the variable value has changed at least once, after putting the application in run mode.
|
1893
|
Data Loggers Management
|
The time rate with which a datalogger recorded data would not always be correct when the recording frequency was less than one second. This problem would particularly happened when setting a base time in milliseconds, which was not a sub-multiple of 1000 msecs (ie. 300, 400, 600, etc).
|
2074
|
Screen Management
|
Movicon would generate an error and close when a screen open as another frame was closed. This error occurred when printing the screen from the screen opened in the other frame using the "Capture and Print" command.
|
2044
|
WebClient
|
A screen enabled with the "Exclusive Write Access" option would still open with two web client stations with write access. This problem could be reproduced by activating the command used for refreshing the page, when a message appeared in the internet browser indicating that the screen was already opened in exclusive mode by another Web client station.
|
2253
|
Real Time DB
|
A driver or OPC group task would not activate when a associated variable, which was from a child project, went into use. Therefore this problem would only show in cased setting child project variables (with the "<ChildName>\<VariableName>" annotation) in a communication driver task or in an item from the the OPC Client DA resource.
|
2244
|
Design
|
Movicon would verify a consumption of GDI objects every time that:
|
2267
|
Screen Objects
|
While the Trend was in run mode a "Break value Areas" would cover an area of valid values. In reality the problem was due to the fact that the break areas should not have been displayed with the Trend in run mode because their positions and sizes can only be calculated when the Trend loads data from the connected data logger, therefore only when passing over from run to stop mode and not the reverse. The break areas are now no longer visible with the Trend in run mode and the recording gaps now get compacted.
|
2047
|
User Interface
|
Instead of the Startup screen showing at project startup the window listing the project startup phases would remain visible.
|
2034
|
Recipes Management
|
The "Recipe Index" and "Recipe Temp" variables must be string type in recipes. In runtime while initializing recipes an error shows in the historical log if "Recipe Index" columns are not purposely assigned a string type variable by the programmer to prevent this error from occurring.
|
1892
|
Real Time DB
|
A variable bit value (ie. byte or word) mapped in a not shared area would not agree with the values of the same variable if not addressed at zero. No variables and corresponding bits agree.
|
1923
|
DOM (Document Object Model)
|
In the "AlarmLoading" event of an alarm threshold the follow alarm properties could not be modified with code:
-
The enabling variable (GetAlarmObject.EnableVariableName)
-
The variable with the threshold value (VariableThreshold)
-
The variable for enabling speech (SpeechEnableVariable)
-
The variable linked to the alarm (GetAlarmObject.VariableName)
Now these properties can be modified but only during alarm initialization (AlarmLoading event), and not afterwards by VBA code.
|
1924
|
Screen Management
|
Compiled ".movscr_c" files are no longer generated in cases involving projects with encrypted resources. This is because the Basic Script code within compiled files did not get encrypted and therefore resource script code could be deciphered back to its origin when opening the file with a text editor.
|
1934
|
Screen Objects
|
Button default structures would not always get acknowledged correctly. When using member variables in "Commands on Release", "Commands on Pressed", "Commands while down" with the ":MemberName" syntax, a 'variable not found' message would show.
|
1695
|
Basic Scripts
|
The WinWrap ver.9 engine would result less performing in respect to the VB Script in some managements or functions. Therefore modifications have been made to the engine to make it more quicker than the VBScript. The following section have been improved:
-
Do...Loop cycles
-
For...Next cycles
-
While...Wend cycles
-
Array Management
-
String Management
-
File Management
-
Mathematical Functions
-
Conversion Functions
|
1623
|
IMDB (In Memory DB)
|
When using IMDB, even if the "Write on disk every..." is set to a very high value, and modifications are done to trace variables in runtime, Movicon would no longer wait for the whole duration of the time set before closing the project after being stopped.
|
1875
|
Screen Objects
|
Problems would verify when refreshing graphics in TAB group object if the screens displaying them had bitmap image backgrounds.
|
1840
|
Design
|
The total byte calculation presented in the hardware key options would calculate all the project's variables first.
Now only those variables that have "fixed I/O address" properties or their "Network Client" property enabled are calculated.
This calculation does not consider variables used in communication driver static tasks and any dynamic links set in the object properties.
|
1314
|
Design
|
A DataLogger window "EventTime" column would not keep to the sizes set when cases where there were also customized columns.
|
1473
|
Data Loggers Management
|
A project would remain pending when exiting when a data logger was set for recording on change, and the variables connect to it changed their values continuously.
|
1317
|
Screen Objects
|
Focus was given to two different objects on screen with the screen contained an ActiveX. This problem would happened after the ActiveX had been focused on.
|
968
|
Design
|
Inserting big symbols on screen from the Symbol Library, Movicon would generate an error within the application.
|
961
|
Screen Objects
|
Listed item selection operations in Combo-box objects could not be cancelled with the ESC key. When moving through the Combo-box's listed items with the scroll arrows, the displayed text would immediately get updated in the display variable.
|
904
|
Networking
|
String members in structure variables were not supported by networking. As a consequence modifications carried out to structure variable strings would not get exchanged between client and server or primary and secondary.
|
923
|
Design
|
Editing script code or IL logic through the appropriate window (Script Explorer, IL Logic Explorer), would not work correctly in muilti-object selections. In fact modifications to IL or script code without being confirmed with OK would get lost when selecting objects that were not part of the multi-selection. In this case only the "master" object, in the multi-selection, acquired the code modifications.
|
991
|
Design
|
Inserting variables in the Watch Window became a very slow process when the project had a very high number of variables. Now when the number of variables exceeds 500, a faster dialog window opens but you can only select all of the structure variable and not its individual members.
|
1007
|
Child Projects
|
The child project screen could not be found when using the command to open screens. This would happen when the child project's "Child Project Option -> Child Project Name" properties were set with value other than null. In this case the selection of a screen from the "Resource Explorer" window in development mode proposed the new name of the child project which could not be found in runtime mode afterwards.
|
853
|
Real Time DB
|
When many variables had been mapped in the same shared area not all would go into use. For example, if one word variable was being used for communicating with the field when objects had been associated to bit variables (mapped in the same shared area), the first would not go into use and the objects did not get updated. Now all variables, in shared areas mapped partly or completely in the same area of another variable already in use, go into use.
|
857
|
DOM (Document Object Model)
|
The "KeyPress" event would not get executed in a screen's drawings, unless associated to that screen's script. Now this event gets associated in drawing which are being focused on.
|
1032
|
WebClient
|
The Combo-Box object now supports the Enter key when used by the Web Client as well.
|
1137
|
Networking
|
The log file of a Network Client project would get filled with messages when the "localhost" Server was not running.
This would happen in the following two situations:
1) When the network Client project started up without the network Server project running
2) When the network Server stopped with the network Client project still connected
This problem has been fixed by introducing a Black List: messages are not printed until the server is Black Listed.
|
1163
|
Design
|
Creating a child project from the parent project, the parent project's constriants would bet used instead of those referring to the project type being created.
|
1297
|
Screen Objects
|
Using the "Script Explorer" window for exploring drawing or screen VBA code, the object list would not get populated with the ActiveXes instantiated with the "WithEvents" clause. For instance, in drawings where the following code line was in the code:
Dim WithEvents Winsock1 As MSWinsockLib.Winsock
The "Winsock1" object would not appear in the object list. As a consequence it became impossible to retrieve that object's specific events automatically as well.
|
1235
|
IMDB (In Memory DB)
|
Data Loggers or Recipes which used the InMemoryDB (IMDB) and contained more than 127j columns would nevertheless get initialized by Movicon. Now an error appears in the log indicating that the number of columns must be reduced. The IMDB has a max limit of 127 columns.
|
2909
|
Screen Objects
|
The "AdaptFont" property has been disabled in the Trend and Data Analysis objects.
|
2869
|
Design
|
Variables could not always be found in parent-child projects in certain IL Logic compilation conditions.
|
2954
|
Screen Objects
|
Following a certain sequences in using the Trend object's "<" and "<<" buttons, the stop button would result disabled until the page got reloaded.
|
3050
|
Design
|
Pressing the "DEL" key on a popup property window field, would close the window and delete the object from the screen.
|
3074
|
IL Logic
|
It became impossible to set a timer with a value higher than "999". Timers can now be set with value up to "100000".
|
3218
|
WebClient
|
When a grid object was used in a Web client page, and selecting a cell with the mouse of keyboard keys, the Grid's title would overlap the text in that cell.
|
3211
|
WinCE OS
|
When a window object was displayed in the Web client, the column headings would no-longer be visible. This problem would only happen with projects run on Window CE devices.
|
2422
|
Screen Objects
|
The ExportToFile function from the TrendCmdTarget used with the XY Trend would generate errors. Now this file is created correctly with fields: VarX, VarY ,Date, Time.
|
2409
|
Screen Management
|
Even though screen objects can be shown outside the workspace, they would become invisible. They now remain visible while in development mode.
|
2462
|
Real Time DB
|
A member of a structure variables in the shared area would not go into use if another variable, which shared its address, was already in use.
|
2478
|
Basic Scripts
|
In runtime the "Scripts" window for each basic script resource in memory displayed the "Unknown" status and the debug window would no longer open by double clicking on the resource.
|
2501
|
Real Time DB
|
A variable's "Reset Statistics" command would not erase data from memory and not from retentive files. Now the retentive file's "Statistic" section gets erased.
|
3245
|
Design
|
Wizards customized in VBA went out of use creating child projects. This error showed: ".PmeDoc.cpp at the line 502. Please contact the Technical support".
|
3309
|
Basic Scripts
|
The basic script editor's 'Replace' command would not work correctly. When using the "Find" function, the "Replace All" command would replace on the word selected at that moment.
|
3324
|
License
|
when inserting any type of software license, the "OPC XML DA Client" and "OPC XML DA Server" options would remain set after re-launching Movicon.
|
2548
|
Screen Objects
|
Alarm blinks in the Alarm Window would not get managed correctly if the list contained a lot of events. Some of the Alarms would not blink.
|
2410
|
Screen Management
|
The parameter file selection command ("Screen - Parameter File command") displayed the generic file browse window. Now it displayed the "Resource Explorer" window with a "Parameter File" Tab which shows the right files only.
|
2423
|
Real Time DB
|
The initial quality of a variable would only set correctly at the first project startup and would set to "Good" at the second project startup.
|
2416
|
Users Management
|
The runtime user file would not get loaded if the password management had not been enabled in the project. Now this file is loaded in accordance to the "Enable Runtime Users" option status.
|
2751
|
Design
|
No error message would appear when the "CEUploadServer.exe" service in WinCE was unable to load "CETransfer.dll" DLL. This led users to believer that everything was working as it should be until it became impossible to upload projects from the development environment. The missing service initialization would only happen following an incorrect installation of components, therefore a very isolated problem.
|
2784
|
Screen Objects
|
Public symbols which do not have the "Preserve Dynamic Properties" option are now managed in a different way. The variables used in symbol animation properties do not get replaced with the public symbol ones. For example, this will allow you to set the color thresholds for background animation in one public symbol and then have many other public symbols which share the same colour thresholds but using different variables.
|
2646
|
Screen Objects
|
Screen object would not keep their sizes when saving the project when they were enabled with one or more zoom levels.
|
2640
|
Users Management
|
When a user's "Logoff Command" command list loaded a child project screen, Movicon would freeze when the user tried to log off.
|
2662
|
Schedulers Resource
|
When renaming "Scheduler" object, its ".sst" persistent file would not cancel.
|
2648
|
Design
|
The tag browser window would show one individual group of variables twice.
|
3150
|
Users Management
|
When inserting new users, their access mask would set a wrong value. This values would be interpreted by Movicon as -1 instead of FFFF. As a consequence, users would incorrectly used the user group access mask they belonged to and not the one indicated in the property window with FFFF.
|
3072
|
Design
|
Screen set with "Bottom to Top" gradients would not get their backgrounds shaded correctly leaving part of the screen unshaded.
|
3065
|
DOM (Document Object Model)
|
The GetActiveUserObject from the UserAndGroupCmdTarget and the GetActiveUserObject from the SynopticCmdTarget would open the same help card.
|
3015
|
Real Time DB
|
The LastAlarmText system variable continues showing the last alarm occurrence when all the alarms had been reset.
|
3003
|
Tools
|
The runtime user editor window would show maximised if the tool had been called with the Movicon "Launch application" command. This would cause problems in positioning controls within the editor window.
|
2996
|
Recipes Management
|
the logic used for loading a recipe was not completely correct causing the recipe load from the data base even when not needed, invalidating all modifications to the recipe variables carried out up to that point. Now the logic used is as follows:
-
If the recipe does not have a temporary index variable, just change index variable to reload recipe
-
If the recipe has a temporary index variable, change the temporary variable so that the recipe gets loaded from the database
|
2978
|
User Interface
|
In the Project Explorer window the "Networking Services - Redundancy" node showed the +/- symbol even when not expandable. This symbol has now been removed.
|
2881
|
Screen Objects
|
The TAB key used in a grid object moved the selected cell in the grid and changed focus over to the next screen object as well. This incorrectly led the user to believe that they could scroll the grid's cells with the TAB keys. Selected grid cells should actually be moved with the arrow keys.
|
2931
|
Design
|
A line would change its orientation when modifying one of its graphical properties. For instance, changing the line's thickness, would also change its orientation. This could only happen when the line had been plotted as if its sizes were negative in its xml definition.
|
1305
|
Screen Objects
|
The Data Logger, Alarm windows etc.. now display three figure millisecond formats, to consent correct item order based on the time column (clicking on the viewer column's title).
|
1280
|
User Interface
|
Using strings for UNICODE projects (ie. Chinese) the "Help" command from the Command List would not work correctly.
|
1254
|
Screen Objects
|
The "Show Milliseconds" option was not managed correctly for all those objects predisposed for retrieving data from a database. When setting this option and using a certain database (MS SQL Server) the milliseconds would show twice in correspondence with each hour.
|
1165
|
Visu+
|
When using licenses not enabled with communication drivers the project log would not show any messages when the project contained communication drivers. The User therefore could not understand why communication was unsuccessful.
|
1010
|
Screen Objects
|
The "Commands on Pressed" button option would be valuated wrongly when a "ON-OFF" or "Impulsive" type.
|
1026
|
PowerHMX
|
The "Sound File" field in a variable' property window was also visible in Power HMI even though not supported.
|
1029
|
Screen Objects
|
The "All" option in the Log Window's "Filter Event Type" field is no longer selectable if the historical log is set for recording on IMDB. Before this option was selectable but would retrieve system messages only due to the fact that the INMemoryDB does not support the UNION clause.
|
1158
|
Design
|
The control on the maximum number of screens and resources insertable in the project would not consider those resources already inserted in the project but had not yet been saved. The resource number limits concern those projects which manage these limits in their constraints file.
|
1096
|
Data Loggers Management
|
The "Record On Change" would activate every time a variable changed. Now as for the "Record On Time Frequency", the "Record On Change" takes into account the Datalogger's enabling variable, variable qualities and any set time frames.
The "Record On Command" would also record even when disabled and if there was a "Recording variable".
Incompatibility:
when loading projects created with previous versions, the "Recording Variable" will only be initialized if the "Record On Command" checkbox has been checked.
|
1122
|
Users Management
|
When setting a control or a resource with a password level not listed in the list box, being between 9 and 1022, the password entry window's title would read as below when opened:
"Enter Password for User Level Administrator"
This text was misdirected now the requested password level displays. Please also consider that if user with the requested password is entered (not administrator level) this will be accepted and work correctly.
|
1111
|
DOM (Document Object Model)
|
The DataLogger-Recipe "DSN" property returned an empty string only if different from default. Now it returns the default value.
|
1114
|
PowerHMX
|
The double click on a screen from the Project Explorer window would not activate the resource in edit mode with resource already opened. This problem would only happen PowerHMI.
|
1115
|
Design
|
The "Border" property of a drawing showed the "None" value for indicating a border with the 1 thickness. Now the "Simple" value indicates the border 1 thickness, while the "Border Size" property is now used for excluding the border when set at zero.
|
470
|
Design
|
Parent project string identifiers could not be retrieved in the string selection window by a child project. This problem has been fixed by introducing a string selection modal window.
|
577
|
Screen Objects
|
The dialog window for selecting images now displays all file types and then lets you choose the one you want (image file types were filtered immediately prior to this change).
|
581
|
Design
|
The "Fonts" group properties were saved in xml files without titles set in the drawing in the following situations only:
|
582
|
Screen Objects
|
A problem with displaying the Trend's graphics would verify when set with many visible pens. The Trend area would appear above the commands in design mode and only hatched in grey in runtime.
This inconvenience has been eliminated by applying a maximum visible pen number limit in the legend.
|
20
|
Real Time DB
|
The Numeric Pad's "1" key was one or two pixels lower then the others in the same row.
|
37
|
Design
|
It was not possible to rename or delete a variable group. Now this can be done and sub groups can now be created within variable groups.
|
72
|
Screen Objects
|
The dynamic tooltip in a display control with enabled "Password Style" option will now always remain deactivated in runtime mode to stop its contents from being displayed.
|
302
|
Screen Objects
|
A Combo-Box list's text size was smaller to the display's test size.
|
329
|
Design
|
During the automatic creation of OPC Items, Movicon would not check for any chars not admitted in the variable's syntax, such as "&%$£". Now all the non admitted chars are substituted with the "_" char in variable names.
|
332
|
Screen Objects
|
Copying a screen containing a "chart" object, the "Editable in Runtime" execution property would reset to the false value in the copied screen, even when this property was set at True in the original.
|
868
|
Historical Log Management
|
When a custom path was specified in the Networking User Path" property in the "Work Folder Settings", the network connection log files got saved in the project folder instead of the specified folder.
|
631
|
Design
|
Filter edit box in the Project Explorer window did not display clearly. It has been improved by giving it a risen effect with a rectangle border and now can be clearly seen within the window.
|
697
|
Design
|
The Properties Window scroll bar (and in displayed Popups) would not adapt when switching over to Easy Mode.
|
707
|
User Interface
|
In the special "_TITLE_GETPTEXT_" string ID which ca be used for the Project User and Password entry window, the "%u" would not get interpreted correctly and the user level would not be placed in the string in runtime mode.
|
719
|
Design
|
Pressing down the "Ctrl++" or "Ctrl--" keys with focus on the Project Explorer window would reduce the size of the window's columns to zero. Now the "Ctrl++" expands the group of items which are selected, while the "Ctrl--" does nothing.
|
1004
|
Screen Objects
|
In the filter windows of the "Data Logger Window", "Historical Log Window" and the "TraceDB Window" controls, dat would be displayed showing months in letters and not figures, based on the language installed in the operating system. This would be problematic for languages such as Chinese. Months are now shown with figures and not letters.
|
988
|
Screen Objects
|
The variable "Address" field would also get disabled for Array type variables mapped in NOT Shared areas also making it impossible to define sizes in bytes for these variable types.
|
989
|
Design
|
It became impossible to copy or paste the text in the Project Explorer's "Filter" field using the keyboard. This could only done by using the relating menu displayed with a right mouse click.
|
887
|
Design
|
Opening the "Field Choice" window for editing columns from "Window" type objects (Alarm window, Historical Log Window", etc.) has been made more userfriendlier.
You will now find a small dot and an arrow at the top right corner of the selected object. Clicking on this dot will invoke the "Open" command. Clicking while pressing down the Shift key will open the "Dynamic Property Explorer" window. Clicking on the arrow will open the Property popup window.
|
958
|
User Interface
|
When a project failed to install a communication driver, the led on the status bar would blink green instead of red.
|
931
|
Screen Management
|
Screen printer would not print images set as screen backgrounds or screen drawings. Now it works correctly when using either the Screen - Print command or the "PrintSynoptic" basic script function.
|
1530
|
Screen Objects
|
The Combo-Box objects in symbols became incapable of loading default symbol structures. When associating structure members to the Combo-Box without the name of the structure variable, associated to the symbol, the Combo-Box could not find the variable.
|
1513
|
Design
|
In the "Font" window which opens when editing Movicon object text, the "Effects" property group would show and could be edited as well. As a consequence the user could set the effects of the text using this window, which was not the correct way of doing things. The effects should be and are, in fact, set in the fields of the Property Window proposed for this purpose.
|
1515
|
Design
|
The Property Window would display the same object several times in the its drop-down list. This would happen when symbols were embedded in other symbols.
|
1453
|
Design
|
When selecting a "Group Box" object and clicking on the General properties "Open" command or double-clicking with Shift key pressed down, the window used for setting Command lists would open. This window has nothing to do with the "Group Box" object which does not support Command list executions on click events.
|
1449
|
Design
|
In design mode, when closing a screen containing a Data Logger window, a save changes? Would always show even though nothing had been changed.
|
1310
|
User Interface
|
Value formatted with floating points would not always be the most compact. Therefore, when these values where displayed within alarm text, with the % form (variable), or in the Watch window, they would not obtain the most compact form.
|
1336
|
User Interface
|
The Watch window and the Output window would lose their positions when switching to runtime mode from design mode. This would happen when the project was not checked to run on full screen. In this case a window which had been docked and latched to the Movicon window during runtime would not longer be latched to the pre-chosen side in the next runtime started from the design mode.
|
1385
|
User Interface
|
the String id 1140 was not correct. The "Failed to start the MovXCE Project: error %lu" text has now been replaced with the "Failed to stop the MovXCE Project: error %lu" text.
|
1433
|
Tools
|
The tool used for editing Runtime users, new users would not show in the dialog window's tree structure list and therefore could not be selected once deselected. This problem would happen after changing the name of the selected user group and then adding a new user.
|
1422
|
Design
|
After "Undo" or "Redo" operations, carried out in relating to the project properties or inserting objects on screen, the project or the screen would not show the '*' indicating resource had been changed.
|
1412
|
Design
|
The "Script Explorer" window would hide again after being activated. This would particularly happen when not docked. In this condition, when selecting a screen or an alarm threshold in the "Project Explorer" window and moving the mouse on top of the "Script Explorer" window"s title it would appear then disappear and then reappear again.
|
1388
|
Design
|
The button in the Variable property's "Dynamic" field, would not confirm variable modifications.
|
1827
|
WinCE OS
|
Values could not be inserted in keys which had different names in the MovXCE.ini file. This problem was linked to the fact that the root element was missing from the XML file's definition, which has now been added in the name of <Settings>.
Incompatibility:
MovXCE.ini files created for the 10.2 version must be modified by adding the <Settings> root tag in order to be read by Movicon 11.
|
1850
|
Comm.Drivers
|
In the dynamic address modification associated directly to a control, the dialog window initiated with default values for the driver. Now it initiated with the current values.
|
1853
|
Design
|
The Screen 'Find/Replace' function would not work correctly often becoming unusable.
|
1790
|
WinCE OS
|
In the Project Upload window in the a remote device, the "Start Device Project" would not stop the instance being run on the device (the command should have first stopped the active instance and then start the project specified in the MovXCE.boot file). This behaviour would show only when the "MS ActiveSync" plugin was used for connecting to the device.
|
1762
|
Screen Objects
|
Executing the "ScreenCmdTarget" VBA interface "PrintSynoptic" method would generate an error in the application if the screen was closed while still running a print process.
|
1742
|
WinCE OS
|
The number of shades has been set to 16 as the default value for all devices with WinCE. This is based on the graphical limits these devices usually have.
|
1696
|
Design
|
The "Copy" and "Paste" command actions from the Script Explorer's button bar were inverted: the "Copy" button would paste and the "Paste" button would copy.
|
1720
|
Design
|
The "Properties Window" in tree view mode would show the same listed item twice.
|
1723
|
Design
|
The following problems would happen using the Symbol Libraries in tree view mode:
-
when creating a new library, a table would display overlapping the tree view impeding access to sub tree nodes
-
when expanding tree nodes, the table would re-design without borders
-
When minimizing or maximizing the Movicon window, the table would disappear and then re-appear overlapping the tree view when using the "Small", "Medium" "Large" display buttons
-
symbols could be inserted into libraries just recreated but the Save and Delete buttons weren't enabled
-
when using the Template Browse command in tree view mode to search for a library, the library selected would load above on top of the tree view
|
1693
|
Screen Objects
|
The display part of a combo-box would not reside.
|
1560
|
Design
|
An error message would display when pressing the TAB key in the Logic Explorer window after having selected a text. Now the test selected is cancelled upon pressing the TAB key (as in Notepad).
|
1667
|
WinCE OS
|
Now, if an error is DBMS raised while recording on logs, data text files are flushed, no matter, when the preset maximum value (Maximum Cache Size) multiplied by 10 is reached.
Only the cache flush in WinCE does not produce text files to avoid the data compact flash becoming saturated if DBMS errors arise.
|
1608
|
Networking
|
Dates and times of messages saved in the network server's debug log file were missing. This type of log file is optional and must be enabled in the network service's advanced settings to create log files in the "NETLOG" folder.
|
1671
|
IMDB (In Memory DB)
|
The "Max. Nr. Records" option has been added to the variable Trace DB. This value is set in the RealTime DB's "Trace DB settings (Audit)" and is valid for all those variables enabled with the Trace.
|
2079
|
WinCE OS
|
Alarms which changed states very quickly in MovXCE projects would occupy too much CPU.
|
2096
|
Screen Objects
|
Invoking a pan view command in Trend objects, their graphics would not get re-designed correctly in those areas where the command was activated. This would happen if curves where moved outside the Trend area displayed.
|
2148
|
Alarm Management
|
The Alarm ACK or OFF events notification would not get send to preset user or user group recipients.
|
1931
|
Design
|
Files in crypted projects containing strings would not get crypted until the string table was modified and saved.
|
1895
|
Screen Objects
|
The color palette window would get redesigned in such a position that when releasing the mouse would involuntarily select any command nearby. The new color palette does not have this problem.
|
1903
|
Data Loggers Management
|
The names of the variable "timestamp" columns could not be customized. The "<VariableName>_timestamp" default value would always get used.
|
1907
|
Screen Objects
|
Inserting a template with the script explorer docked, would cause variables enclosed between the "#" chars not to be replaced in the code with the variables added in the project. This problem happened only if there were structure variable enclosed between "#" chars in the VBA code.
|
1890
|
Basic Scripts
|
"Unicode" chars could not get inserted when editing basic scripts with their editor, or using the Script Explorer window.
|
2035
|
DOM (Document Object Model)
|
The below listed "PmeDocCmdTarget" interface properties relating to child projects were in both read/write but now are in read only:
|
2269
|
Design
|
Vertical or horizontal line objects would not move towards the left or the top using the mouse with the "Snap to grid" option active.
|
2251
|
Networking
|
The first time that a dynamic NET variable is connected to a server (with no other project variables connected) the communication between client and server would breakdown and could only be restored when the server unblacklisted.
|
2207
|
Screen Objects
|
When no scales where visible in the Trend, the data and time area would get cut when touching the left margin.
|
2345
|
Data Loggers Management
|
The SQL query for altering a Data Logger table failed when a column containing the number of variable updates was added ("Add Num. Updates Column" property). This problem was due to the fact that the SQL query did not return the name of the column to be added only the type:"ALTER TABLE Log1sec ADD int". As a consequence the table got deleted and then re-created, losing all previously recorded data.
|
2369
|
Real Time DB
|
Inserting variable names with spaces at the beginning or at the end of the name, Movicon would take it for basic expression. Now spaces are ignored.
|
3295
|
Design
|
Screens opened with the "Open Frame (multi-monitor)" command, would not adapt to the sizes of the window containing them if the command was double-clicked.
|