ID
|
TOPIC
|
PROBLEM SOLVED
|
3889
|
Screen Objects
|
Some images set in screen drawings would not always show, even though these files were physically present in the computer. This problem started happening in the 958 build with the 1724 case resolution.
|
4000
|
Networking
|
Project termination would freeze while stopping the network servers when returning back to design mode.
|
3879
|
Basic Scripts
|
Using a function's "ByRef" parameter in a "For...Loop" cycle, a basic script motor exception would occur freezing Movicon.
|
3933
|
Setup
|
The setup installed the "StoreUnicodeProject" value in the "General" key for the Movicon application, even when the operating system was not in Unicode. As a consequence all the projects created with the Movicon wizard, would get checked as unicode.
|
3934
|
Design
|
The project's "unicode" option would not get market when being created in a unicode operating system (i.e. Windows Chinese). This problem would occur using the "Empty Project" and "Template Project" wizards.
|
3905
|
Real Time DB
|
A DataLogger or TraceDB would not record variable values correctly, if the variable happened to be integer type with the default format containing a decimal point. This problem first started occurring with the build 1010.
|
3907
|
Setup
|
The setup of the reduced Movicon version (PowerHMI) would not install the right registry keys for opening the "PowerHMI.exe" file in automatic when double clicking on a file with a ".movprj" extension.
|
3942
|
Tools
|
The tool used for importing and exporting variable to and from CSV files (CSVTagIE.exe), would no longer manage the "Initial Background Color" and "Initial Foreground Color" properties. As a consequence, after having exported and re-imported the variables, many controls used the color black color for the background and text-edge colors. This problem started happening with the tool version installed with the Movicon build 1012.
|
3969
|
License
|
Variables in shared areas would get counted on the license even when not used for communicating. This problem would happen when another variable in the same area and address went into use for communicating. This problem first started happening in the Movicon 1010 build.
|
4065
|
WinCE OS
|
Recipe values in floating point, FLOAT, would not get re-read correctly when the floating point was used as a decimal separator.
|
4058
|
Tools
|
The alarm statistics report print or preview commands would display a blank report or a "Invalid Parameter Type passed" error message. This would happen in cases where the Windows' international settings were set with a different set of values to those set in "Italy" and in cases where filtered data was inserted when print or preview command was invoked.
|
4060
|
Design
|
Pressing OK in the XML explorer window would save any symbol script code in one line only. This would cause problems when executing this code in runtime.
|
4071
|
Alarm Management
|
A "No error message available" error message would appear when switching over to runtime from design mode. This only happened when alarms were deleted or disabled in the project which had been active in the previous runtime. This problem first started happening in the Movicon build 1010.
|
4041
|
IMDB (In Memory DB)
|
The IMDB (InMemoryDB) would not manage data in floating point correctly in ".dat" retentivity files. In fact these values should have been saved using the decimal point instead, even when other international settings used the comma. As this didn't happen, when retentive values in the ".dat" file were loaded, only the integer part of those values with floating points would get loaded.
|
4011
|
Design
|
When using Movicon in French or German, various strings used in the "Empty Project" and "Template Project" wizards would not get completely displayed.
|
4074
|
Setup
|
The Historical Log and Trace window "Print" buttons would not send reports to the printer for printing, unless the report was specified in the appropriate window's property. This problem was due to the fact that the setup had not installed the "HisLog.repx" and "TraceDB.repx" files searched by Movicon for print operations.
|
3836
|
Users Management
|
Movicon would always log on a domain user as a user belonging to the "Guests" group. This problem would arise if the domain user had not been inserted in the local domain user list as well.
|
4094
|
Screen Objects
|
The bottom circular gauge cursor could not be moved with the mouse. This seemed to happen when one of the two bottom gauge's "Start Angle" or "End Angle" properties was set with a negative value.
|
4034
|
Alarm Management
|
Not all names of alarm retentive files were correct. This verified when an alarm was created with the same name of a project variable (new function introduced with the 1010 build). This made all alarms share just the one retentivity file in stead of having one each.
|
4035
|
Tools
|
When transferring a project to Windows XP/VISTA, files compiled with the "_c" prefix would not delete. As a consequence, the project run locally would behave differently in respect to the one in remote. This problem has been solved in the TCP plugin.
|
4047
|
Screen Objects
|
Setting a meter or slider's minimum limit dynamically with a variable value different to zero, would make the value set in the variable based on the object cursor's position incorrect.
|
4073
|
Screen Objects
|
An error in the Chinese, English, German and French resources caused the "Print" command in the historical log or trace window not to send any "HisLog.repx" and "TraceDB.repx" files, installed by Movicon, to the printer.
|
3996
|
Setup
|
Dialog windows for customizing Movicon tool bars and menus remained in English even when the development's IDE was set to another language.
|
4029
|
Alarm Management
|
One alarm would get create twice at the project startup. This happened when the alarm had the same name of a project variable and if that variable included the same alarm as template in its list.
|
3581
|
Screen Objects
|
An object's transparency level would not get displayed correctly, following certain operations carried out in design or runtime.
|
3600
|
Screen Objects
|
The 'update', 'delete' and 'save' commands would not work in the grid object if its column titles were changed caused by the project's string table. It is not possible to change languages for modifying grid column headings, otherwise this would jeopardize its correct way of working.
|
3800
|
Screen Objects
|
Commands on click set in an object (new option introduced with version 11) would not work when the object was embedded in a symbol.
|
3823
|
Screen Management
|
A project's default menu or accelerator would not get loading changing pages. This problem would show when using the "Renaming Management" and in cases where the Start screen had been renamed.
|
3869
|
Basic Scripts
|
The "DateDiff" function would return an incorrect result in cases where the parameters were in the last half second of the day.
|
1178
|
Networking
|
A variable connected to a network server would remain set if managed with a impulsive button on the client side.
|
3944
|
Setup
|
Installing the "QJ71E71_TCP" driver in Windows CE would fail using the connection from the Windows "start" menu. This problem was inherent to the cab file list contained in the "QJ71E71_TCP.SSDK.ini" file from the "MovXCESetup" sub folder.
|
3913
|
Schedulers Resource
|
A "Hour plan" scheduler would not read the default holidays file (".defhol") when set with holidays.
|
3935
|
Setup
|
The SQL Server 2005 Express version installed with the setup in the Movicon installation DVD was not supported by Windows VISTA.
|
3936
|
Design
|
Symbols in libraries would not animate even though set with the animation option. This problem has been solved, but the only animations which can be managed for the time being are:
- the bar in meter objects
- the Trend area in the Trend object (not the data analysis)
- Texts in display and combo box objects
- Dynamic animations: scale, text - show value, gradual filling, dynamic images (only if embedded in symbol), dynamic back and text color - text and edge color
|
4006
|
User Interface
|
The tooltip which showed for the properties window's "Alphabetic" command displayed an incorrect text written in Italian but was written correctly in the other languages.
|
3971
|
Design
|
The "Dynamic Property Explorer" window would show the same variable twice in the tab listing all the variables used by the symbol selected.
|
4070
|
Design
|
The "Empty Project" and "Template Project" wizard used for creating projects would not set the unicode in the XML file heading (<?xml version="1.0" encoding="UTF-16"?>). As a consequence the project creation script would generate an error saving the xml resource, when using Movicon in Chinese.
|
4050
|
Design
|
The commands for creating report web pages were not described correctly using Movicon in Italian.
|
4045
|
Design
|
The refactoring window would only control the presence of the first variable in cases where the basic script expressions contained more then one variable.
|
4046
|
Design
|
The refactoring window would show the dame error twice when selecting a screen resource.
|