|
ID
|
TOPIC
|
PROBLEM SOLVED
|
|
4109
|
Networking
|
The "ConnectVariable" function from the "NetworkClientCmd" basic interface would always wait for the arrival of a valid value from the network server before returning. In fact this coincided with waiting for the timeout, set in the Client, to lapse. An optional parameter has now been entered to force a asynchronous connection, meaning that this function can now return without waiting for the variable to synchronize with the network server.
|
|
3895
|
User Interface
|
A string identifier would not always be searched for in the right context in parent-child projects. Now within Parent-child project context, the child project searches for local project strings first and if none are found it searches further afield in father projects if any.
|
|
4347
|
OPC Communication
|
Reading an OPC XML DA Server item would fail if the OPC server had not sent/dispatched the tag with the value quality requested by Movicon.
|
|
3987
|
WebClient
|
Movicon would go into error and close during a project arrest if a web client had connected. This problem would occur systematically when the web client happened to showing a screen page with the IP Viewer object; however this was apt to happen with other objects.
|
|
4023
|
User Interface
|
A modal window would no longer get selected using the mouse while opened on screen when a logic changed the background screen in background. In Windows XP/VISTA this problem only occurred with windows within Movicon: numeric pad, alphanumeric pad, logon window, change password window. In Windows CE this problem would occur also with project modal screen windows.
|
|
4085
|
Design
|
Movicon would go into error and close when attempting to add a "Tab Group" object to the symbol library.
|
|
4110
|
Screen Management
|
The processor occupied nearly 100% memory in the presence of intense graphic animations on panels with Window XP embedded with a low performing hardware. This would greatly slow down performances with managing animations and interactivity.
|
|
4150
|
Screen Objects
|
The "IP Viewer" object was not able to visualize images from some Axis 206 type cameras. This problem would occur for those video cameras which verified that the "User-Agent" parameter was not in the "<Product>/<Version>" standard formation.
|
|
3822
|
WinCE OS
|
The logon window would go in the background in respect to the Movicon main window if recalled with the "GetPasswordFromLevel" or "GetPasswordFromUser" functions from a basic script source.
|
|
3962
|
Basic Scripts
|
There would seem to be two problems with using the structure or array variables with the "IntelliSense" option within a script:
a) Movicon would raise an error and close when calling help (F1 key) with the array or structure variable selected in an script code editor window
b) In runtime the basic script would raise an error with the "0x8000ffff" code if the variable started with the "Array" name.
|
|
3838
|
Screen Objects
|
A Combo box's horizontal bar would not get managed correctly. It now comes based on the longest text sizes in the drop down list.
|
|
106
|
Screen Management
|
The project's user interface would freeze when the "ShowLongOperationDialog" function closed while unloading the screen from memory. For instance, this would happen if an event object executed a change page command while a "ShowLongOperationDialog" was open that had been called from an object within a screen just that minute closed. Now upon the closure of the screen that called the "ShowLongOperationDialog", the user interface reactivates to avoid freezing when the screen is deactivated and destroyed.
|
|
212
|
ODBC
|
Movicon could not create an ODBC connection towards the SQL Server Express 2005. The "2" value is now also supported for the "General\UseDefaultSQLServer" key that forces Movicon to expressly use the SQL Server Express with the "SQL Native Client" ODBC Driver.
|
|
4356
|
Data Loggers Management
|
Movicon would delete a data logger table at project startup. This would occur when the data logger received the record on variable command straight upon project startrup.
|
|
4296
|
Screen Objects
|
Some of the "TrendCmdTarget" basic script interface functions would provoke an error in the Movicon application. The following functions have been disabled for the Data Analysis because they are only supported by the Trend:
ImportFromFile
ImportFromClipboard
ExportFromFile
ExportFromClipboard
CopyLegendToClipboard
SetSamplesValue
SampleValue
SampleDateTime
GetCursorDateTime
GetCursorDateTimeMsec
GetCursorDateTimeString
GetFirstValidDateTime
GetFirstValidDateTimeMs
GetLastValidDateTime
GetLastValidDateTimeMs
GetCursorPenValue
|
|
4158
|
Users Management
|
The "NumActiveUsers" member would not decrease correctly when a web client disconnected from the server.
|
|
4198
|
Design
|
Some automatic operations which inserted many variables in the project, i.e. communication driver importer, would take a long time to do so.
|
|
4186
|
Design
|
Some of the strings from the object toolbox were not entered correctly in Chinese.
|
|
4218
|
Design
|
The "Dynamic Property Inspector" window deleted variables, set for drawing script notifications, if the script code was empty when existing with "OK" from the window. This could have also been the main cause of an error which arose while the Movicon application was closing in cases where the project explorer window had expanded the drawing's structure.
|
|
4221
|
Design
|
A symbol would corrupt if modified using the XML code explorer window.
|
|
4456
|
License
|
Some minor problems have been fixed in the bytes-in-use count for licenses. These particular problems would occur in certain conditions, above all in client-server projects.
|
|
4464
|
Screen Management
|
when using the "Office 2007" style (which is the predefined value in Movicon 11), the screen MDI TAB bar would stop showing in runtime. As a consequence, the 'Show MDI Tab' screen option would not be supported without changing the Movicon workspace style.
|
|
4212
|
Real Time DB
|
The comment (Audit Trail) in a structure variable trace would not consent the retrieval of information on which member of the structure variable had been changed. Structure variable members now remain indicated even when a comment is set.
|
|
4213
|
Setup
|
Uninstalling Movicon would also remove those drivers used for reading the license in USB/Parallel keys. As a consequence, the license could no longer be seen by other versions of Movicon installed on the same operating system.
|
|
4122
|
Design
|
A certain amount of memory space would get occupied every time the new variable editor closed.
|
|
4185
|
WinCE OS
|
The "Pipe" object would not get drawn correctly in Windows CE. In addition, the editor consented the "Polybeizier" to be entered even when not supported in Windows CE.
|
|
4244
|
Screen Objects
|
Clicking on a editable display without associated a variable would not let it enter into edit mode. This problem arose only when Movicon had to manage the "Show Pad" option for that display (a standard situation with Windows CE). As a consequence, it proved difficult to use the "OnTextChanging" or "OnTextChanged" events in editable displays.
|
|
4287
|
Screen Objects
|
Entering into edit in a scheduler window, grid or design object, the editing text size was not always correct. This problem started showing in the 1010 build and did not occur with editable displays.
|
|
4340
|
Screen Objects
|
Data at the start and end of the time axis could not be retrieved for the data analysis so we have added the following new properties in read only to deal with this:
dateFromCurrent
dateToCurrent
dateFromCompareCurrent
dateToCompareCurrent
|
|
4314
|
Basic Scripts
|
Various "UserCmdTarget" and "UserAndGroupCmdTarget" interface functions and properties could not be used properly from a basic script resource but only from script code within a screen or screen object. This problem started occurring with the 1010 build.
|
|
4315
|
Screen Objects
|
While a grid object was connected to a text file, the "Insert" command added a row with a numeric value at random in the first field.
|
|
3375
|
Design
|
When opening a screen in edit mode to add an empty row in the screen's XML definition using the 'XML code explorer', the objects on screen would no longer be selectable. In addition, when modifying object positions and sizes with the "XML code explorer", the objects would not display with their new settings on screen.
|
|
3750
|
Design
|
An error would display in the "DevExpress" modules when editing a report containing a graphic. This problem has been fixed by upgrading the "DevExpress" to the 8.2 version.
|
|
3409
|
Screen Objects
|
You can now export date in CSV files using the "ExportToFile" function from the "TrendCmdTarget", but importing data from CSV files is still not working correctly: it cleans the graphic without displaying the values.
|
|
3456
|
Screen Objects
|
Editing cells in grid and scheduler window objects became a problem. For instance, when starting to edit without pressing 'enter' or F2, the characters corresponding to the pressed key would validate straight away exiting the cell from edit mode.
|
|
4151
|
User Interface
|
Using a screen as a window for carrying out user logon operations, when pressing the "Cancel" button this window would appear within Movicon. This would only happen if the logon request window had been called by a basic code with the "GetPasswordFromUser" function from the "UIInterface" interface.
|
|
4155
|
Basic Scripts
|
The "StringFromID" function from the "PmeDocCmdTarget" basic interface would return a string of a different language to the one active when the basic script was used. This would happen in those projects which had their user management active and when a user was logged on. This problem started with 1010 build.
|
|
4147
|
Screen Objects
|
The "Ctrl+R" (reset all) accelerator from the alarm window would not work.
|
|
4148
|
Screen Management
|
A project with the "Pre-load screens" at startup" option enabled would not startup correctly if the "Show status bar" option had not been enabled as well. The project would start up but the startup screen would not show until focus was taken away and given to the Movicon window.
|
|
4016
|
WebClient
|
A combo box would not close when clicking on one of its items from web client.
|
|
4076
|
Report Management
|
The report designer would not stop recreating the connection to the database within the report. As a consequence, any further connections or tables added to the report would get lost. A message now appears asking the user whether the table and the structure within the report should be recreated as well.
|
|
4406
|
WebClient
|
A screen displayed on a web client page would appear with sizes smaller to the browser window sizes. This problem occurred when using the option for adapting image sizes to the size of the browser window and when a later version of the JAVA runtime 1.6.0.07 has been installed.
|
|
4410
|
Users Management
|
The list of modified passwords would not load at project startup when the runtime users management had been disabled. This problem started occurring with the 1010 build.
|
|
4421
|
Design
|
Pressing the "OK" key in the XML code explorer window applied the modifications but not the settings as confirmed. As a consequence the "OK" button remained active and when focusing on another window, the modifications were applied once again.
|
|
4396
|
Screen Objects
|
When changing focus from one cell to another in the gird object, the text from the previously focused cell would get inserted in the cell being focused. This problem occurred only when the "Show control window" option" was active and the cell changed while having its value was being edited.
|
|
4079
|
Report Management
|
The following error message would show when closing the report designer of a report: "The process cannot access the file '...' because it is being used by another process."
|
|
3991
|
Real Time DB
|
An editable field would not focus when opening the Audit Trail window when tracing a variable. As a consequence, the editable field had to be selected first in order to enter a comment.
|
|
3999
|
Screen Objects
|
Border lines indicating selected objects would remain visible even though the object was invisible in runtime. This problem occurred in those objects that were being dragged or resized at that moment.
|
|
4117
|
Report Management
|
Bands could not be added when creating a report. Now, the Report header, Report detail and Report footer bands are added for default.
|
|
4120
|
Real Time DB
|
The Audit Trail comment window tracing a variable, would not accept and insert comments without any text written in them. Now only written comments, with text, are inserted when confirmed with 'OK'.
|
|
4121
|
Report Management
|
The report designer continued using the "Table" name as the name of the table and not the real table name in the database. This, however, did not compromise the correct execution of the report.
Incompatibility:
Opening a report created with the previous version, you need to re-assign the table column which now has a new name to each report field.
|
|
4133
|
Design
|
In the "Empty Project" and "Template Project" wizards for creating projects, only missing character controls were carried out in the path and not in the project name.
|
|
4134
|
Design
|
When creating new projects with the "Empty Project" and "Template Project" wizards no message appeared when the value supplied in the screen default color fields was incorrect.
|
|
4135
|
Design
|
The "Enter" key would not close the dialog window in the "Empty Project" and "Template Project" wizards used for creating projects.
|
|
4136
|
Design
|
The control for existing projects in the "Empty Project" and "Template Project" wizards for creating projects has been moved to allow the user to return back and change the project name.
|
|
4137
|
Design
|
All error messages in the "Empty Project" and "Template Project" wizards used for creating projects would not report the name of the application in the title.
|
|
3521
|
Design
|
The "Resource Browser" window that opens when wanting to select a parameter resource to use for a "Screen" command, also allowed the "Basic Script" and "Menu" tabs to be selected in addition to the "Parameter File" tab.
|
|
3376
|
Design
|
A symbol in a screen would disappear when its position or its size was modified with the XML code explorer window. This symbol would return visible when closing and reopening the screen.
|
|
3377
|
Design
|
When using the "XML Code Explorer" for modifying screen symbol settings, these setting would not be visible straight away. As soon as these modifications were confirmed, the symbol's contents would disappear from screen and only its border remained visible.
|
|
3402
|
Real Time DB
|
Compiling a variable which had just been associated to a data logger, alarm or event, the corresponding compiled file (.movdlrec_c, .movalr_c e .movevt_c) did not get deleted. As a consequence, the project continued to work with the previous list when in runtime mode.
|
|
2036
|
User Interface
|
A tooltip would open when opening a modal window, screen or pad with the name of the screen in background.
|
|
2586
|
Design
|
When a symbol ungrouped the "Position" properties of the objects that were used to compose the symbol remained disabled.
|
|
4236
|
Screen Objects
|
The "TrendCmdTarget" interface's "DataFilterBy" and "DataSortBy" properties could not be completely exploited because they would cancel the data filter which was applied in the WHERE clause based on the time ranges selected in the Data Analysis.
|