|
ID
|
TOPIC
|
PROBLEM SOLVED
|
|
4581
|
Recipes Management
|
Recording a whole variable recipe with the default decimal format, i.e. "x.x" would cut off the less significant values because the decimal part of the number would only get considered. For instance, if the variable had the "12" value, when the record command activated, the value would get written in the database as "1".
|
|
4544
|
Design
|
The "Open #Uses" command would send the Movicon application in error. This problem occurred when the basic script to be opened contained a high number of rows.
|
|
4555
|
Real Time DB
|
A variable's daily, weekly, monthly and yearly statistics would not get zeroed.
|
|
4567
|
Screen Objects
|
The "HourSelectorCmdTarget" basic interface's "Scheduler" property always showed the scheduler set in design mode and not the actual one in use by the scheduler window.
|
|
4570
|
Screen Objects
|
The template based on the "Scheduler Window" object from the "Schedulers" symbol category, has been straightened out in the basic script code to resolve a series of problems that occurred when users were given the possibility to change things in the window with the scheduler in edit mode.
|
|
4803
|
ODBC
|
The "datetime" columns in databases would get created with a "datetime2" using SQL Server 2008. This then compromised data interpretations by objects preset to display historical data.
|
|
4768
|
Real Time DB
|
A new "ScrollLastAlarmText" DWORD value has been added to the Movicon "General" keys which allows the scroll in active alarms to be deactivated in system variables. By doing this the system variable's "LastAlarmText" member behaves the same way it did in the Movicon 10.2 version.
|
|
4772
|
Comm.Drivers
|
Sending a project in run from design mode problems would occur with a driver's static tasks when associated to a structure variable. This problem showed only when going into runtime from design mode after the static tasks had been edited.
|
|
3563
|
WinCE OS
|
Information regarding international settings would not get retrieved correctly in Windows CE 6.0.
|
|
4659
|
Screen Objects
|
The "Scheduler" object would not initialize correctly if not displayed when loading the screen. Once made visible it became unusable.
|
|
4668
|
WinCE OS
|
The MovCE.exe executable of build 1015 compiled for Windows CE devices from the ARM microprocessor family, occupied about 3 MB of memory more than the previous version. This problem was due to the missing option for optimizing executable code in the compilation phase to make it thinner to execute.
|
|
4861
|
Screen Objects
|
A pen's scale would be set automatically with the "Scale > Auto" option following a zoom operation.
|
|
4838
|
Screen Objects
|
The "IP camera viewer" object would not connect to protected cameras. In fact the user name set in the object would not get used in runtime to validate access to the protected telecamera.
|
|
4965
|
ODBC
|
Using the ODBC driver for an Interbase database, the data and time columns would get created as "DATE" type and not "TimeStamp" type. As a consequence only the date and not the time would get memorized. Now these columns are now also created by Movicon as "TimeStamp" type with the "Interbase" database.
|
|
4956
|
User Interface
|
Using the IDE in the German language, column headings of a CSV file created with a Trend object were not correct. The date and time headings were inverted.
|
|
4963
|
Screen Objects
|
A problem was found with the 'Pens' button basic script code in templates based on the Trend and Data Analysis objects. When confirming modifications, some of the pens' settings would get lost when executed.
|
|
4901
|
Recipes Management
|
The updating of a recipe did not save string fields that had been set with an empty string.
|
|
4661
|
Design
|
The "Move Next" and "Move Previous" move command tooltips were not correct using the IDE in Italian.
|
|
4654
|
User Interface
|
Changing language would not get managed correctly in Window CE when user logged off. As a consequence, when a user logged off the last language that was activated when no user was active would get restored.
|
|
4657
|
Historical Log Management
|
The output of a project's log file would get interrupted when the Alarm Dispatcher when into action or when any other application was put into run mode with the Movicon "Launch Application" command.
|
|
4807
|
Basic Scripts
|
The data structure types set with OCX were not supported in the Movicon basic script language.
|
|
4525
|
WinCE OS
|
The luminous square buttons would show with inverted animation in Windows CE. Meaning that when the variable was set at zero the button would light up and viceversa.
|
|
4541
|
IMDB (In Memory DB)
|
Immediately after a project run, a variable trace in IMDB would not longer display from the "Trace DB Window" until the variable changed value at least once.
|
|
4575
|
Screen Objects
|
Schedulers that were added in runtime with the "Scheduler Window" object did not support holidays. Now they do and treat holidays using the hour plan set for Sunday if "Support Holidays" is not enabled in the object.
|
|
4573
|
PowerHMI
|
The online help call in the "PowerHMI" basic function browse window would not work; it would in fact search for the "PowerHMX.chm" file instead of the "PowerHMI.chm" file.
|
|
4588
|
User Interface
|
The Movicon window would go into background when closing the application that had been called with the "Launch Application and wait" or "Show Textual report" command.
|
|
4629
|
Design
|
Pressing the "End" button in the wizard used for creating "Template Projects", the project would get created empty. Now these projects are created with those set for default in the wizard.
|
|
1144
|
Screen Management
|
A modal screen would not closed on the "CLOSE" command when the name of the sub folder in which the screen belonged to was specified. This screen now closes correctly by specifying the screen name only or leaving this field empty.
|
|
3343
|
Screen Objects
|
A 3D button with a "ON-OFF" mechanism mistook the background colour with the text colour when the variable was set differently to zero. This behaviour would make the button's text nearly invisible. Now this button lights up when the variable is set, and the background and text colours no longer get swapped over by mistake.
Incompactibility:
The 3D buttons were set in a certain way so that you could play around with colours so that texts and background colours swapped over with each other. Now due to this new feature to illuminate buttons you may need to reset the back colours originally set with the previous Movicon version.
|
|
4766
|
DOM (Document Object Model)
|
The "AlarmCmdTarget" return value was declared instead of the "AlarmThresholdCmdTarget" in the "GetLastAlarmOn" function's definition from the "PmeDocCmdTarget" basis interface.
|