|
ID
|
TOPIC
|
FIXES
|
|
18976
|
Alarm Management
|
During Runtime the Alarm templates would not get managed when the project was saved after a resourse had been modified. They could not be triggered and shown in the Alarm Window or recorded.
|
|
17264
|
Design
|
The contextual Help would not be opened in the properties of all the project's OPC UA Client resources.
|
|
18008
|
Design
|
When selecting a group of objects and modifying the Tab Order with menu commands or with the '+' and '-' keys on the numeric keypad, the operation now is executed in all the objects belonging to the group at the same time as indicated below:
· "Move First": the selected group of objects is placed in the foreground whereby the objects maintain their order within the group and are repositioned starting from the highest tab number.
· "Move Last": The selected group of objects is placed in the backgound in respect to the others but maintain their order within the group.
· "Move Next": all the selected objects are promoted to the next level to the one they belong to.
· "Move Back": all the selected objects are move to the previous level to the one they belong to.
|
|
18217
|
Design
|
No Help reference opened when pressing the 'F1' key on keyboard in the 'Edit Font' property to open the font selection window based on the langauge of the Project.
|
|
16086
|
Design
|
When pressing the 'F1' key in the "Event Cache" of an Alarm Resource, an error message would show: 'Impossible to startup Guide" 'Impossibile avviare la Guida'.
|
|
18342
|
Networking
|
Problems with subscribing and unsubscribing variables, which had side effects that significantly slowed down Server notification to Clients, have been fixed.
|
|
18571
|
OPC
|
In cases where Redundant projects used the OPC Client after a communication error occurrence with the OPC Server in the Secondary project, the Secondary variable values would not get refreshed with those present in the Primary project when the connection was restored.
|
|
17831
|
OPC Client
|
When the OPC Server DA exposed items whose names began with a figure or an underscore, the Movicon OPC Client DA browser would create items and varaibles with invalid syntax. Now names of the OPC DA Server items and variables beginning with a figure or underscore are now given a prefix using the 'V' character .
|
|
18641
|
OPC Communication
|
Some values of the ValueRank attribute were not managed when browsing the OPC UA Server's address space. Alcuni valori dell'attributo ValueRank non venivano gestiti, durante il browse dell'address space del Server OPC UA.
|
|
18489
|
OPC Communication
|
The OPC UA Client could not connect to an OPC UA Server using a secure connection. In order to create a connection at runtime, the Server's certficate must be included among those trusted by the Client. The folder containing the trusted certificates, as well as the path where the Client certificate is stored, is shown in the "ClientUAConfig.xml" configuration file. The path for Windows CE relates to the project folder: [projectpath]\UA Application\certs.
|
|
17716
|
Screen Management
|
Delays in selecting objects would occur when the Gestures option had been enabled as well.
|
|
17546
|
Screen Management
|
When loading a page containing a Trend, the mouse's hourglass icon would remain visible until the screen was touched.
|
|
18127
|
Screen Object
|
The XY Trend would not show the cursor's 'x' value correctly unless the scale of the curves had been set to Logarithmic.
|
|
17506
|
Screen Objects
|
IThe Numeric or Alphanumeric Pad would lose focus when there were several screens in the project that has bee loaded in memory.
|
|
17713
|
Screen Objects
|
Analysing data using the Data Analysis object would cause the "Point found with invalid Date and Time in the Data Logger' error message to appear in cases where one or more records had data with NULL values. This error would also occur even when the date and time values were correct and not NULL.
|
|
17903
|
Screen Objects
|
The "Web Browser" symbol and the "Browser Setting" were not modal.
|
|
17559
|
Screen Objects
|
Scolling rows within a Window Object would result inaccurate and over reactive when the Gestures function had been enabled in the project.
|
|
18024
|
Screen Objects
|
In cases using the IMDB engine for the project's Historical Log, the Historical Log window's Print button and options would get hidden because they were incompatible for use with the IMDB.
|
|
19081
|
Symbols Library Templates
|
The 'Duty Manager' symbol created and managed variables with the wrong names which then effected the compilation of the time combobox list that showed empty as a result.
|
|
18400
|
Tools
|
It is now possible to access the Runtime Users file (.rtusers) from another project by using the 'Enable Runtime Users security' property located among the advanced 'Users and User Groups' resource options. This can be done providing that a 'User Runtime Access Code' common to several projects has not been set in the same advanced 'Users and User Group' resource. If this is not the case, the Runtime Users file will be encrypted with this access code otherwise the file will be encrypted with the unique code created in the relation to that project.
|
|
18480
|
Tools
|
Invoking 'PrnWndCE' too in Windows CE from Mocicon using a 'Screen' command, an 'Invalid Window Handle' error message would be returned.
|
|
18989
|
Tools
|
The automatic "RestoreFlushData" tool no longer eliminates the Data Logger Data flush file if input on the DB fails during the Restore phase.
|
|
18267
|
Tools
|
The Report-Recipe command (which uses the ReportViewerNet.exe tool) to Export a straReport, set for extracting data from the last month or year, would not exported export data of the last day.
|
|
18725
|
Tools
|
The CSVTagIE.exe Tool used to import or export the project variables in CSV files would ignore the Trace or OPC UA options that were activaed in the variables during the exportation phase.
|
|
18998
|
WinCE
|
The system "_SysVar_:ActiveScreen" variable would not get updated with the focused Screen's ID in Windows after a Modal or Frame popup closed and screens set to be kept in memory were preloaded at project startup. The Popup Screen ID is now set correctly in the "_SysVar_:ActiveScreen" even for those cases where a custom modal window is set to request Password or replace the Numeric or Alphanumeric Pad. In the last case mentioned, any interface updates in the initial screen are temporarily suspended while the Popup screens remain active.
|
|
18406
|
WinCE OS
|
If a Display object had been enabled in the Multitouch Windows CE systems, the Numeric Pad would also open when clicking the Display externally.
|