|
ID
|
TOPIC
|
PROBLEM SOLVED
|
|
7483
|
Alarm Management
|
Some alarm transactions would go missing if the variable associated to the alarm change too quickly.
|
|
6273
|
Basic Scripts
|
An error would show in the MouseMove() definition when using the .NET directive in the Movicon script. This problem has been fixed with the WinWrap 9.3 version that for the time being is provided by Progea on request if needed.
|
|
7384
|
Basic Scripts
|
Recording the Historical Log IMDB would cause the Drivers tables to recreate for each new entry, zeroing the already existing contents.
|
|
7397
|
Basic Scripts
|
Sub definitions would not get acknowledged when setting script for .Net syntax with the WinWrap Basic 9.30.61 version.
|
|
7249
|
Basic Scripts
|
Too much memory space was used when using XML object in Movicon .NET script. This problem has been fixed with the WinWrap 9.3 version that for the time being is provided by Progea on request if needed.
|
|
7439
|
Comm.Drivers
|
When starting a project up, a DataLogger set for record on change would record twice.
|
|
7659
|
Comm.Drivers
|
When exchanging an array type that wasn't in byte with the Communication Driver it would not work properly. Only the first 10 bytes would get exchanged.
|
|
7534
|
Comm.Drivers
|
If the "Prompt Control Window' option was disabled in the Historical Log, TraceDB display windows etc, their columns could not be resized.
|
|
7398
|
Data Loggers Management
|
When inserting a basic script expression in a DataLogger, the field would get created in text type if the table had been created in development mode.
|
|
7330
|
Design
|
In certain conditions, the mouse click with the CTRL pressed down on an "Embedded Screen" would raise an error in the Movicon application.
|
|
7421
|
Design
|
DataLogger data could not be recovered from a midlet application.
|
|
7335
|
Design
|
When using a recipe and evoking the "Create Recipe Screen" command a message would show notifying that screen resource had been edited outside and would user like to reload it.
|
|
7379
|
Design
|
In certain conditions Movicon would raise an error while working without snapping to grid.
|
|
7391
|
Design
|
When inserting resources, such as Screens, Basic Script, etc., which contained a dot in their names, the xml. file would not get created when saving the project.
|
|
7420
|
Design
|
A Child project's _SysVar_:LastAlarmText system variable did not have any values in either the Parent or Child projects.
|
|
7378
|
Design
|
The "Area" field for Alarm commands was active for all types of commands instead being active just for "Ack All" and "Reset All".
|
|
7299
|
Design
|
A variable's "Enable Data Statistics" property gave wrong advice.
|
|
7651
|
Design
|
Problems occurred with public symbols in certain situations after selecting the Public Source Container within a screen.
|
|
7600
|
Design
|
Movicon would raise an error after reloading the String Table which had been edited with an external editor beforehand (such as the StringImpExp.exe tool).
|
|
7329
|
Design
|
When selecting a control which activated the text format bar, each time the mouse moved the toolbar would get redesigned, or at least the two combo-boxes within would flicker.
|
|
7323
|
Design
|
The size of Trend pens in statistical value settings would not work correctly.
|
|
7664
|
Design
|
In certain cases, using a project in SourceSafe mode, when Checking-in one resource, all the resources got requested for checking in.
|
|
7324
|
Design
|
The "Template Project" wizard plug-in created some objects, such as the Trend and Alarm Windows, with the wrong settings.
|
|
7552
|
Historical Log Management
|
Log files created after ODBC errors would sometimes not get formatted correctly. For example, message text would get divided on two lines.
|
|
7358
|
IL Logic
|
IL logic could not be used for variable starting with the letter 'K'.
|
|
7679
|
Networking
|
A Client project's TraceDB window could not recover historical data from the Server if the variable's table name had been customized.
|
|
7442
|
Networking
|
A Client project created with Parent/Child architecture with set redundancy options on the Child project, Movicon would freeze when project was being aborted.
|
|
7673
|
Networking
|
The GetVariableDescription function would always return an empty string if executed in a Client project created with Parent-Child architecture.
|
|
7357
|
OPC Communication
|
The error message that Movicon generated when an OPC item could not be found in the OPC server's address space, did not report the name of the item.
|
|
7356
|
OPC Communication
|
It was not possible to put a structure variable composed with a certain number of "Bit" elements in communication with a OPC Server Tag in Bool Array type with the same number of elements that the structure variable had.
|
|
7616
|
Real Time DB
|
Launching a project from development mode, variables set in the shared area (input, output or flag), would get considered as belonging to the NOT shared area.
|
|
7676
|
Report Management
|
If a Report created with Report Designer connected to a DataLogger that contained a space in its Datalogger name, the "dataset" would not get created correctly therefore data would not get loaded.
|
|
7340
|
Screen Management
|
A Screen that had been set with more that '1' instance would not open more than once. this would happen if the screen had been closed clicking the "X" on the title bar and not the close button on screen.
|
|
7080
|
Screen Management
|
On screen object animations were not sychronized with the basic script manager.
|
|
7630
|
Screen Management
|
After selecting the "Close and Return Back" it became no longer possible to select a screen name in the "Screen" field.
|
|
7387
|
Screen Management
|
When setting a screen alias, an object contained within an embedded screen would not read the alias value.
|
|
7405
|
Screen Management
|
When inserting the "Capture and Print" command and specifying the name of the screen to be printed, renaming this screen with a new name, this new name would not be applied by the command.
|
|
7388
|
Screen Objects
|
The Trend, upon opening the screen, would not load runtime data when the "Read Data in Background" option had been set.
|
|
7337
|
Screen Objects
|
Local container screen variables of an 'Embedded Screen' would not get read by the Embbed Screen.
|
|
7265
|
Screen Objects
|
In the Data Analysis even though a pen was displayed respecting the 'TimeStamp' column, selecting data, by applying a filter for instance, it would always get selected respecting the "LocalCol" column.
|
|
7264
|
Screen Objects
|
In the Data Analysis the Pen points would get drawn differently when quality = NOT good, according whether the "TimeStamp" or "TimeCol" column was being used.
|
|
7263
|
Screen Objects
|
If a pen's "Use TimeStamp" option had been enabled in the Data Analysis, its points would be put into order according to the TimeStamp column, but the lines were drawn compliant to the TimeCol.
|
|
7274
|
Screen Objects
|
Executing the "Set Screen Alias" command would raise and error in Movicon if not the last command on the list.
|
|
7292
|
Screen Objects
|
The Data Analysis's Progress Bar would have problems while refreshing from Client and every so often would indicate that values were wrong.
|
|
7287
|
Screen Objects
|
In the Data Analysis, displaying data within the same second, the time axis would not align to the times reported in the point labels.
|
|
7286
|
Screen Objects
|
Milliseconds would not display in the Data Analysis in correspondence to the time axis notches even though enabled to do so.
|
|
7332
|
Screen Objects
|
The "GetLastValidValuePosition" method from the "TrendCmdTarget" would not work correctly.
|
|
7333
|
Screen Objects
|
When a screen was kept in memory (Keep in Memory enabled) it was impossible to force shut down the operating system.
|
|
7377
|
Screen Objects
|
A Tab Group object would not display the screen's name in the tab properly.
|
|
7471
|
Screen Objects
|
Even though the "Show Control Window" option had been disabled, the "List" of a Combo-Box, would always show at the forefront even though its tab order was lower than another object's.
|
|
7267
|
Screen Objects
|
In certain conditions only some of the legend pens would get displayed in the Data Analysis object, leaving out the selected pen's point labels.
|
|
7183
|
Screen Objects
|
Display window column font alignments would not get managed correctly for window columns.
|
|
7256
|
Screen Objects
|
In the Recipe Manager Window, the recipe selection combo-box list would always stay with default sizes even though the "Text Font" property had been changed.
|
|
7360
|
Screen Objects
|
The text displayed in the "display" part of a Combo-Box would not update when the list of items had changed.
|
|
7618
|
Screen Objects
|
A problem occurred with a screen inserted with diverse "Embedded Screens" overlapping each other, when clicking on the border of an embedded Screen at the forefront, the others behind also responded to the click.
|
|
7502
|
Screen Objects
|
In certain conditions an object's "Enable Zoom" visibility property would not work correctly. For example, this object would not disappear if its size became smaller than the percentage set.
|
|
7381
|
Screen Objects
|
The Trend's curves would not get drawn correctly when the "Read Data in Background" option had been enabled.
|
|
7316
|
Screen Objects
|
It became difficult scrolling data in the Data Analysis when selecting the "Month" date range.
|
|
5443
|
Screen Objects
|
A problem arose in the Recipe Manager Window when using the keyboard to edit a cell. The first character entered would get overwritten by the second character entered.
|
|
7464
|
Screen Objects
|
A Data Analysis would invalidate regions outside its area when it had pens with rectangular styles.
|
|
7512
|
Screen Objects
|
The "Enable Size" visibility property did not have effect in composed symbols.
|
|
7451
|
Screen Objects
|
There were problems in WinCE in displaying texts used with the "Overlap Image/Text" enabled.
|
|
7438
|
Screen Objects
|
In the Data Analysis, if the "Load Data in Separate Thread" option had been enabled, problems would occur when setting the time scale to "Adjust to values" or "Absolute Ranges.
|
|
7444
|
Screen Objects
|
In particular conditions, if the Trend had an automatic scale, data would not get displayed when the Trend switched from Stop mode to Run mode.
|
|
7478
|
Setup
|
The list of DevExpress assemblies installed with Movicon 11.2 were not all correct.
|
|
7450
|
Setup
|
The "DevExpress.XtraRichEdit.v9.3" component would not get registered while installing Movicon, later causing problems in Web report.
|
|
7514
|
Setup
|
The "Time.msxz" library would get installed also after it had been renamed in "Clocks.msxz".
|
|
7413
|
Tools
|
Even though the "Acknowledge Scada Alarm" option from the Alarm Dispatcher's VOICE plug-in had been enabled, the alarm's Reset would not work if in the OFF(ACK) state.
|
|
7400
|
Tools
|
When using the alphanumeric pad to insert the password in the EditUsr.exe tool, the actual password would be revealed instead of being concealed.
|
|
7372
|
Tools
|
Problems would occur while importing an ".csv" file in to the Movicon String Table if strings contained the "<" or ">" chars, being chars interpreted as opening/closing of xml tags.
|
|
7480
|
User Interface
|
The window for entering the software license became unusable in panels with 640x480 or smaller resolutions. This has been fixed so when pressing the "CTRL" key on the command to open the License Requirement window you will find a button for opening the soft key window in reduced size through which to enter the software code.
|
|
7448
|
User Interface
|
In certain conditions Movicon would raise an error during the stop mode of projects launched with the MoviconRunTime.exe.
|
|
7433
|
User Interface
|
In certain cases evoking the "Wait Time" system command while closing the project would raise an error in Movicon.
|
|
7399
|
Users Management
|
The first Logon operation performed after project startup, would not execute the logon script linked to the user.
|
|
6925
|
Users Management
|
A Runtime User profile would not load when logging into the Windows domain. Only Users created in development mode could gain access to the Windows Domain.
|
|
7369
|
Users Management
|
The window for user password re-entries would also accept blank password entries. This would happen if the "Min. Password Length" property had been set to zero. Now this property requires at least one character when set at zero.
|
|
7479
|
WebClient
|
Using a Web client connected to a Server project running on WinCE, would use up a lot of memory navigating screens if they had been set with a value minor to 100 in their "We Client Quality" properties.
|
|
6938
|
WebClient
|
The WebClient midlet in BlackBerry phones was not working properly.
|
|
6803
|
WinCE OS
|
Movicon could not continue with new recording when having problems with ".sdf", database files in WindowsCE. Now when this happens, the files are cancelled and then created again.
|
|
7454
|
WinCE OS
|
In certain situations the Numeric Pad would not show the minimum and maximum limits correctly.
|